This API runs asynchronously. A 202 response means Insider One accepted the operation, not that the event has changed. Test with one event on one test user first.
Check the result in the InOne panel
Check the result that Insider One sends to your hook_url. Error codes, such as EVENT_NOT_FOUND and MULTI_MATCH, arrive there.
Save the operation_id from the response.
Go to Audience > User Profiles and search for the user.
Open the Events tab and find the event you deleted or updated.
Wait a few minutes, then refresh the tab. A deleted event no longer appears. An updated event shows the new values.
If the event does not change, check that the event name, timestamp, and user identifier match the original event exactly.
Interpret the response
Response | Meaning | What to do |
|---|---|---|
202 with operation_id | Insider One accepted the operation and is processing it. | Keep the operation_id for support requests, then verify on the Events tab. |
409 | A lock exists for the same user and event. The lock is released when the previous operation finishes, usually after a few seconds. | Retry after a short delay. |
400 | The request failed validation, e.g., no timestamp and no filters, a system field in filters, or an unmapped filter parameter. | Read the error code, fix the request, and resend. |
429 | You exceeded the limit of 250 requests per minute. The limit counts delete and update requests together. | Wait, then resend the request. |
A 202 does not guarantee that a matching event exists. If no event matches, the panel shows no change.
Reproduce a failure in Postman
Open the endpoint page and select Run in Postman. The Insider One Postman documentation opens at that endpoint.
In the top right corner of the Postman documentation, select Run in Postman.
In the Fork collection into your workspace window, select Fork Collection. Postman opens the collection in the Postman app or in your browser.
Select the environment that holds your API key and partner name.
In the Body tab, select raw and paste the payload from your integration.
Select Send and compare the status code and response with your integration log.
Change one field at a time, such as the event timestamp, until the response matches the failure.
Remove the API key and personal data before you share the request or response.
To trigger a known error on purpose, remove both timestamp and filters from the body. The API returns 400.
For more information, see Insider One APIs in Postman and API Status and Error Codes.