# Data Events Everything about your Data Events ## Submit a data event - [POST /events](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-events/createdataevent.md): You will need an Access Token that has write permissions to send Events. Once you have a key you can submit events via POST to the Events resource, which is located at https://api.intercom.io/events, or you can send events using one of the client libraries. When working with the HTTP API directly a client should send the event with a of . When using the JavaScript API, adding the code to your app makes the Events API available. Once added, you can submit an event using the method. This will associate the event with the Lead or currently logged-in user or logged-out visitor/lead and send it to Intercom. The final parameter is a map that can be used to send optional metadata about the event. With the Ruby client you pass a hash describing the event to , or call the method directly on the current user object (e.g. ). | Type | Description | Example | | :-------------- | :-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | :-------------------------------------------------------------------------------- | | String | The value is a JSON String | | | Number | The value is a JSON Number | | | Date | The key ends with the String and the value is a Unix timestamp, assumed to be in the UTC timezone. | | | Link | The value is a HTTP or HTTPS URI. | | | Rich Link | The value is a JSON object that contains and keys. | | | Monetary Amount | The value is a JSON object that contains and keys. The key is a positive integer representing the amount in cents. The price in the example to the right denotes €349.99. | | When submitting events for Leads, you will need to specify the Lead's . - We currently limit the number of tracked metadata keys to 10 per event. Once the quota is reached, we ignore any further keys we receive. The first 10 metadata keys are determined by the order in which they are sent in with the event. - It is not possible to change the metadata keys once the event has been sent. A new event will need to be created with the new keys and you can archive the old one. - There might be up to 24 hrs delay when you send a new metadata for an existing event. The API may detect and ignore duplicate events. Each event is uniquely identified as a combination of the following data - the Workspace identifier, the Contact external identifier, the Data Event name and the Data Event created time. As a result, it is to send a second granularity Unix timestamp in the field. Duplicated events are responded to using the normal code - an error is not thrown, however repeat requests will be counted against any rate limit that is in place. ### HTTP API Responses - Successful responses to submitted events return with an empty body. - Unauthorised access will be rejected with a or response code. - Events sent about users that cannot be found will return a . - Event lists containing duplicate events will have those duplicates ignored. - Server errors will return a response code and may contain an error message in the body. ## List all data events - [GET /events](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-events/lisdataevents.md): > 🚧 > > Please note that you can only 'list' events that are less than 90 days old. Event counts and summaries will still include your events older than 90 days but you cannot 'list' these events individually if they are older than 90 days The events belonging to a customer can be listed by sending a GET request to with a user or lead identifier along with a parameter. The identifier parameter can be one of , or . The parameter value must be . - - - (this call can be used to list leads) The parameter value should be url encoded when sending. You can optionally define the result page size as well with the parameter. ## Create event summaries - [POST /events/summaries](https://developers.intercom.com/docs/references/rest-api/api.intercom.io/data-events/dataeventsummaries.md): 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.