You can create a message that has been initiated by an admin. The conversation can be either an in-app message, an email or whatsapp.
🚧 Sending for visitors
There can be a short delay between when a contact is created and when a contact becomes available to be messaged through the API. A 404 Not Found error will be returned in this case.
This will return the Message model that has been created.
🚧 Retrieving Associated Conversations
As this is a message, there will be no conversation present until the contact responds. Once they do, you will have to search for a contact's conversations with the id of the message.
Intercom API version.
By default, it's equal to the version set in the app package.
You can create a message
The kind of message being created. Values: in_app, email or whatsapp.
The time the message was created. If not provided, the current time will be used.
- The production API serverhttps://api.intercom.io/messages
- The european API serverhttps://api.eu.intercom.io/messages
- The australian API serverhttps://api.au.intercom.io/messages
- message_type: `email`.
- message_type: `inapp`.
- message_type: `whatsapp`.
- user message created
- lead message created
- admin message created
- admin whatsapp message created
- No body supplied for message
- No subject supplied for email message
- No body supplied for email message
curl -i -X POST \
https://api.intercom.io/messages \
-H 'Authorization: Bearer <YOUR_TOKEN_HERE>' \
-H 'Content-Type: application/json' \
-H 'Intercom-Version: 2.16' \
-d '{
"from": {
"type": "user",
"id": "6762f2341bb69f9f2193bc17"
},
"body": "heyy",
"referer": "https://twitter.com/bob"
}'admin message created
The type of message that was sent. Can be email, inapp, facebook or twitter.
- user message created
- lead message created
- admin message created
{ "type": "user_message", "id": "403918396", "created_at": 1734537780, "body": "heyy", "message_type": "inapp", "conversation_id": "613" }