Home//
REST API Reference
/- Creates a conversation
Add tag to a conversation
Remove tag from a conversation
List all conversations
Retrieve a conversation
Update a conversation
Search conversations
Reply to a conversation
Manage a conversation
Run Assignment Rules on a conversation
Attach a contact to a conversation
Detach a contact from a group conversation
Redact a conversation part
Conversation
Conversation List Item
Creates a conversation
You can create a conversation that has been initiated by a contact (ie. user or lead).
Sending for visitors
You can also send a message from a visitor by specifying their user_id or id value in the from field, along with a type field value of contact. This visitor will be automatically converted to a contact with a lead role once the conversation is created.
This will return the Message model that has been created.
Security
bearerAuth
Intercom-Versionstring(intercom_version)
Intercom API version.
By default, it's equal to the version set in the app package.
Default:"2.9"
Enum:"1.0""1.1""1.2""1.3""1.4""2.0""2.1""2.2""2.3""2.4"
Example:2.9
The title of the email. Only applicable if the message type is email.
Example:"Thanks for everything"
A list of image URLs that will be added as attachments. You can include up to 10 URLs.
- The production API serverhttps://api.intercom.io/conversations
- The european API serverhttps://api.eu.intercom.io/conversations
- The australian API serverhttps://api.au.intercom.io/conversations
- conversation created
- Contact Not Found
curl -i -X POST \
https://api.intercom.io/conversations \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: 2.9' \
-d '{
"from": {
"type": "user",
"id": "6657ab116abd0164c24b0d4d"
},
"body": "Hello there"
}'conversation created
The type of message that was sent. Can be email, inapp, facebook or twitter.
Enum:"email""inapp""facebook""twitter"
Example:"inapp"
Response
{ "type": "user_message", "id": "403918237", "created_at": 1717021458, "body": "Hello there", "message_type": "inapp", "conversation_id": "329" }