Duplicate events for API

Question

Dear Sir / Madam, We are developing an integration with Intercom via the API and events. Recently, prob starting about 1 - 2 weeks ago, we noticed that Intercom send 3 copies of every event. We followed the guideline to send back the ok() on every event we processed, but somehow the duplicate events still come on every event. Did the guideline change? This used to work well but something seems to have changed recently. Best

Jacques Reynolds · Accepted Answer

Hey ​@Emma A.👋 Jacques here from Support Engineering!The issue you're experiencing with duplicate events may be related to the event de-duplication process within Intercom's API. The API is designed to detect and ignore duplicate events, which are identified by a combination of the App identifier, the User identifier, the Event name, and the Event created time. It is recommended to send a second granularity Unix timestamp in thecreated_atfield to ensure uniqueness. If duplicate events are still being sent, it's possible that there may be an issue with the timestamp or another part of the event identification process. Despite duplicates, the API will respond with a202 Acceptedcode, and these repeat requests will count against any rate limit in place.If you've been following the guidelines and are still receiving duplicates, it might be worth reviewing the event identification data you're sending, particularly thecreated_atfield, to ensure it meets the required granularity and uniqueness.For further guidance on event metadata types and to ensure you're following the most current practices, you can refer to the Event Metadata Types documentation here:Event Metadata Types.This may require some digging so feel free to reach out to our support team so they can do some more troubleshooting on this for you! :)

Join the Intercom Community 🎉

Intercom Customers and Employees

Login to the community

Intercom Customers and Employees

Scanning file for viruses.

This file cannot be downloaded