accounting/accounts3

accounting/addresses2

accounting/attachments3

accounting/balancesheets2

accounting/cashflowstatements2

accounting/companyinfos2

accounting/contacts3

accounting/creditnotes2

accounting/expenses3

accounting/incomestatements2

accounting/invoices3

accounting/items2

accounting/journalentries3

accounting/payments3

accounting/phonenumbers2

accounting/purchaseorders3

accounting/taxrates2

accounting/trackingcategories2

accounting/transactions2

accounting/vendorcredits2

auth1

connections1

crm/companies3

crm/contacts3

crm/deals3

crm/engagements3

crm/notes3

crm/stages2

crm/tasks3

crm/users2

ecommerce/customers2

ecommerce/fulfillments2

ecommerce/orders3

ecommerce/products3

events1

fieldMappings6

filestorage/files3

filestorage/folders3

filestorage/groups2

filestorage/users2

linkedUsers5

marketingautomation/actions3

marketingautomation/automations3

marketingautomation/campaigns3

marketingautomation/contacts3

marketingautomation/emails2

marketingautomation/events2

marketingautomation/lists3

marketingautomation/messages2

marketingautomation/templates3

marketingautomation/users2

passthrough2

projects2

sync4

ticketing/accounts2

ticketing/attachments3

ticketing/collections2

ticketing/comments3

ticketing/contacts2

ticketing/tags2

ticketing/teams2

ticketing/tickets3

ticketing/users2

webhooks5

ticketing/contacts

Retrieve Contact

Retrieve a Contact from any connected Ticketing software

get/ticketing/contacts/{id}

Path parameters

idstring required

id of the contact you want to retrieve.

Query parameters

remote_databoolean

Set to true to include data from the original Ticketing software.

Headers

x-connection-tokenstring required

The connection token

Response

prev_cursorstring nullable required

next_cursorstring nullable required

Example response

{
  "data": [
    {
      "name": "Joe",
      "email_address": "joedoe@acme.org",
      "phone_number": "+33 6 50 11 11 10",
      "details": "Contact Details",
      "field_mappings": {
        "fav_dish": "broccoli",
        "fav_color": "red"
      },
      "id": "801f9ede-c698-4e66-a7fc-48d19eebaa4f",
      "remote_id": "id_1",
      "remote_data": {
        "fav_dish": "broccoli",
        "fav_color": "red"
      },
      "created_at": "2024-10-01T12:00:00Z",
      "modified_at": "2024-10-01T12:00:00Z"
    }
  ]
}

Changes

Changed in 4 of the 18 revisions of this API.367

Aug 5, 2024ca213ae36b7f171See the full diff
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the /// response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ▲
  the /// response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ○
  the endpoint scheme security bearer was removed from the API
  api-security-removed
This revision also has 5 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 5, 2024167edd5346ec25See the full diff
- ▲
  the /// response's property type changed from string to object, and format from date-time to no format for status
  response-property-type-changed
- ▲
  the /// response's property type changed from string to object, and format from date-time to no format for status
  response-property-type-changed
- ○
  the endpoint scheme security bearer was added to the API
  api-security-added
- ○
  the response property /// became required for the status
  response-property-became-required
- ○
  the response property /// became required for the status
  response-property-became-required
- ○
  the response property /// became required for the status
  response-property-became-required
- ○
  the response property /// became required for the status
  response-property-became-required
This revision also has 8 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 3, 20249d25bd589fe917See the full diff
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property //// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became nullable for the status
  response-property-became-nullable
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the response property /// became optional for the status
  response-property-became-optional
- ▲
  the /// response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
- ▲
  the /// response's property type changed from object to string, and format from no format to date-time for status
  response-property-type-changed
This revision also has 4 changes that name no endpoint, such as unreferenced schemas being removed. See the revision's changelog
Aug 1, 2024414c3e999e0b1See the full diff
- ○
  the endpoint scheme security bearer was removed from the API
  api-security-removed

Full history