First steps
Courses
Events and Behaviour Tracking
User Data
- Email Builder Review
- Designing your email
- Creating a Synchronized Module
- Setting Responsivity
- Building Smart Containers
- Creating a Gmail Promotions Annotation
- Adding a Rollover Effect
- Adding a Background to an Email
- Adding Anchor Links
- Adding a Video to an Email
- Adding a Table to an Email
- Adding a Custom Font
- Adding Social Media Buttons
- Editing HTML and CSS
- Working with “Images” block
Omnichannel
Automation
Personalization
Analytics
Multilanguage Campaigns
Recommendations
API
Security and Compliance
Integration
Website Integration
Receiving App Inbox Messages to a Webhook
Instead of sending API requests to our system to get App-inbox messages for your contacts, you can receive the list of all the available App-Inbox messages to your webhook.
We can configure for you the maximum number of messages for your contacts. The default number is 1,000.
Note
We can send the messages to your webhook only for the contacts having externalCustomerId assigned.
Webhook Requirements
You have to send us the webhook URL, where you want to receive the messages, and the basic authorization (optional).
HTTP method | POST |
---|---|
Authentication (optional) | Basic |
Format |
|
App Inbox Message
The messages you receive have the following format:
{
"externalCustomerId" : string, // Receiver identifier
"id" : UUID, // Interaction ID. Used to set status
"createdDate" : long, // Timestamp in milliseconds
"title" : text,
"content" : text,
"image" : string, // URL
"link" : string // URL
"category" : string // Message category
}
Response HTTP Status Codes
Code | Description |
---|---|
200 OK | Successful request processing. |
401 Forbidden | Authentication failed. The system retries such requests. |
429 Too Many Requests | The message number limit is exceeded. The system retries such requests. |
400 Bad Request | An issue with payload processing. The system does NOT retry such requests. |
500 Internal Server Error 502 Bad Gateway 503 Service Unavailable |
Temporary processing issues. The system retries such requests. |