List instances of a custom object type. Three modes are supported:
- No filter — returns all instances for the type.
references_contact_id— returns instances associated with the given contact.references_conversation_id— returns instances associated with the given conversation.
When external_id is provided, returns a single matching instance (not a list).
Security
bearerAuth
Intercom-Versionstring(intercom_version)
Intercom API version.
By default, it's equal to the version set in the app package.
Default:"2.16"
Enum:"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"
Example:2.16
- The production API serverhttps://api.intercom.io/custom_object_instances/{custom_object_type_identifier}
- The european API serverhttps://api.eu.intercom.io/custom_object_instances/{custom_object_type_identifier}
- The australian API serverhttps://api.au.intercom.io/custom_object_instances/{custom_object_type_identifier}
curl -i -X GET \
'https://api.intercom.io/custom_object_instances/Order?references_contact_id=string&references_conversation_id=string&external_id=string&page=0&per_page=150' \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Intercom-Version: 2.16'successful
pagesobject(Pagination Object)
The majority of list resources in the API are paginated to allow clients to traverse data over multiple requests.
Their responses are likely to contain a pages object that hosts pagination links which a client can use to paginate through the data without having to construct a query. The link relations for the pages field are as follows.
dataArray of objects(Custom Object Instance)
An array of Custom Object Instance objects.
Response
{ "type": "list", "pages": { "type": "pages", "page": 1, "per_page": 20, "total_pages": 1 }, "total_count": 2, "data": [ { … }, { … } ] }