Locations Endpoint
Endpoint Actions
Create Record
POST /v2/locations
Update Record
PUT /v2/locations/{id}
View Single Record
GET /v2/locations/{id}
View Record List
GET /v2/locations
Note: Filters can be used to search for Locations by including the columns you want to filter on as URL parameters. i.e. /v2/locations?field=value&field2=value2
Delete Record
DELETE /v2/locations/{id}
Fields
Name | Format | Min | Max | Required on Post (Create) | Required on Put (Update) | System Generated | Comments |
---|---|---|---|---|---|---|---|
id | string | 24 | 36 | ✔ | Unique id of location | ||
aba | string | 9 | 9 | Aba / Routing | |||
account_number | string | 0 | 32 | Account number | |||
address1 | string | 0 | 32 | Address 1 | |||
address2 | string | 0 | 32 | Address 2 | |||
branding_domain_id | string | 24 | 36 | GUID for Branding Domain | |||
city | string | 0 | 100 | City name | |||
contact_email_trx_receipt_default | boolean | If true, will email contact receipt for any transaction | |||||
created_ts | integer | 10 | 10 | ✔ | created timestamp | ||
dda | string | 3 | 32 | Dda | |||
default_ach | string | 24 | 36 | GUID for Location's default ACH Product Transaction | |||
default_cc | string | 24 | 36 | GUID for Location's default CC Product Transaction | |||
developer_company_id | string | 24 | 36 | GUID for Developer Company | |||
email_reply_to | string | 60 | Used as from email address when sending various notifications | ||||
fax | string | 10 | 10 | Fax number | |||
location_api_id | string | 24 | 36 | Location api ID | |||
location_api_key | string | 36 | 36 | ✔ | Location api key | ||
location_c1 | string | 128 | Can be used to store custom information for location. | ||||
location_c2 | string | 128 | Can be used to store custom information for location. | ||||
location_c3 | string | 128 | Can be used to store custom information for location. | ||||
modified_ts | integer | 10 | 10 | Timestamp for last modification | |||
name | string | 1 | 64 | ✔ | Name of the company | ||
office_phone | string | 10 | 10 | Office phone number | |||
office_ext_phone | string | 0 | 10 | Office phone extension number | |||
parent_id | string | 24 | 36 | ✔ | Location GUID of the parent location | ||
recurring_notification_days_default | integer | # of days prior to a Recurring running that a notification should be sent | |||||
receipt_logo | string | 0 | 256 | Receipt logo | |||
show_contact_files | boolean | If set to true will show "Files" tab on Contact | |||||
show_contact_notes | boolean | If set to true will show "Notes" tab on Contact | |||||
state | string | 100 | State name | ||||
ticket_hash_key | string | 36 | 36 | ✔ | Ticket hash key | ||
tz | string | 0 | 24 | Time zone | |||
zip_code | string | 5 | 10 | Zip code of the city |
Expands (Related Records)
For detail on how to use Expands on an Endpoint, please visit the Expands (Related Records) page.
Related Record | Expand ID |
---|---|
Branding Domain | branding_domain |
Created User | created_user |
Developer Company | developer_company |
Product Transaction | product_transactions |
Product Recurring | product_recurring |
Product File | product_file |
Parent | parent |
Terminals | terminal |
Expand Examples
Below are some examples of “expanding” this endpoint to one of the above related records.
Parent Location
GET /v2/locations/xxxxxxxxxxxxxxxxxxxxxxxx?expand=parent
Developer Company
GET /v2/locations/xxxxxxxxxxxxxxxxxxxxxxxx?expand=developer_company
Branding Domain
GET /v2/locations/xxxxxxxxxxxxxxxxxxxxxxxx?expand=branding_domain
Using Multiple Expands
You can use multiple expands on an endpoint. Simply include them separated by a comma(s) like so:
GET /v2/locations/xxxxxxxxxxxxxxxxxxxxxxxx?expand=branding_domain,developer_company,parent