Intercom API (2.11)
The intercom API reference.
https://api.intercom.io/
https://api.eu.intercom.io/
https://api.au.intercom.io/
- The production API server
https://api.intercom.io/contacts/{contact_id}/notes
- The european API server
https://api.eu.intercom.io/contacts/{contact_id}/notes
- The australian API server
https://api.au.intercom.io/contacts/{contact_id}/notes
- curl
- Node.js
- Ruby
- PHP
- Python
- Java
- Go
- C#
- R
curl -i -X POST \
https://api.intercom.io/contacts/123/notes \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: 2.11' \
-d '{
"contact_id": "667d60978a68186f43bafd9e",
"admin_id": 991267493,
"body": "Hello"
}'
Successful response
String representing the object's type. Always has the value note
.
Represents the contact that the note was created about.
Admins are teammate accounts that have access to a workspace.
String representing the object's type. Always has the value admin
.
Identifies if this admin is currently set in away mode.
Identifies if this admin is set to automatically reassign new conversations to the apps default inbox.
Identifies if this admin has a paid inbox seat to restrict/allow features that require them.
This object represents the avatar associated with the admin.
Image for the associated team or teammate
{ "type": "note", "id": "34", "created_at": 1719492759, "contact": { "type": "contact", "id": "667d60978a68186f43bafd9e" }, "author": { "type": "admin", "id": "991267493", "name": "Ciaran103 Lee", "email": "admin103@email.com", "away_mode_enabled": false, "away_mode_reassign": false }, "body": "<p>Hello</p>" }
- The production API server
https://api.intercom.io/contacts/{contact_id}/segments
- The european API server
https://api.eu.intercom.io/contacts/{contact_id}/segments
- The australian API server
https://api.au.intercom.io/contacts/{contact_id}/segments
- curl
- Node.js
- Ruby
- PHP
- Python
- Java
- Go
- C#
- R
curl -i -X GET \
https://api.intercom.io/contacts/63a07ddf05a32042dffac965/segments \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Intercom-Version: 2.11'
{ "type": "list", "data": [ { … } ] }
Request
You can fetch a list of subscription types that are attached to a contact. These can be subscriptions that a user has 'opted-in' to or has 'opted-out' from, depending on the subscription type. This will return a list of Subscription Type objects that the contact is associated with.
The data property will show a combined list of:
1.Opt-out subscription types that the user has opted-out from. 2.Opt-in subscription types that the user has opted-in to receiving.
- The production API server
https://api.intercom.io/contacts/{contact_id}/subscriptions
- The european API server
https://api.eu.intercom.io/contacts/{contact_id}/subscriptions
- The australian API server
https://api.au.intercom.io/contacts/{contact_id}/subscriptions
- curl
- Node.js
- Ruby
- PHP
- Python
- Java
- Go
- C#
- R
curl -i -X GET \
https://api.intercom.io/contacts/63a07ddf05a32042dffac965/subscriptions \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Intercom-Version: 2.11'
Successful
A list of subscription type objects associated with the workspace .
The state of the subscription type.
A translation object contains the localised details of a subscription type.
The localised name of the subscription type.
The localised description of the subscription type.
An array of translations objects with the localised version of the subscription type in each available locale within your translation settings.
The localised name of the subscription type.
The localised description of the subscription type.
Describes the type of consent.
{ "type": "list", "data": [ { … }, { … } ] }