POST /events/summaries
Create event summaries for a user. Event summaries are used to track the number of times an event has occurred, the first time it occurred and the last time it occurred.
Servers
- https://api.intercom.io
- https://api.eu.intercom.io
- https://api.au.intercom.io
Request headers
| Name | Type | Required | Description |
|---|---|---|---|
Content-Type |
String | Yes |
The media type of the request body.
Default value: "application/json" |
Intercom-Version |
String | No |
Possible values:
Default value: "2.12" |
Request body fields
| Name | Type | Required | Description |
|---|---|---|---|
event_summaries |
Object | No |
A list of event summaries for the user. Each event summary should contain the event name, the time the event occurred, and the number of times the event occurred. The event name should be a past tense 'verb-noun' combination, to improve readability, for example |
event_summaries.count |
Integer | No |
The number of times the event occurred. |
event_summaries.last |
Integer | No |
The last time the event was sent |
event_summaries.first |
Integer | No |
The first time the event was sent |
event_summaries.event_name |
String | No |
The name of the event that occurred. A good event name is typically a past tense 'verb-noun' combination, to improve readability, for example |
user_id |
String | No |
Your identifier for the user. |
How to start integrating
- Add HTTP Task to your workflow definition.
- Search for the API you want to integrate with and click on the name.
- This loads the API reference documentation and prepares the Http request settings.
- Click Test request to test run your request to the API and see the API's response.