Answers to common questions about the Event Delete & Update API, grouped by topic. For the full endpoint reference and request examples, see Create an Event Delete or Update Request.
Scope and availability
Can I delete or update multiple events in one request?
No. Each request targets one event for one user. To correct multiple events, send a separate request for each one.
Can I delete or update events from the InOne panel?
No. This version is API only. There is no panel interface for delete or update operations.
Can I change the event timestamp?
No. Timestamps are immutable; they cannot be changed via update. The timestamp is used as an event identifier and must remain as originally recorded.
Can I delete or update email, push, or other channel delivery events?
No. Events produced by Insider One channels, including email, SMS, WhatsApp, Web Push, App Push, session, InApp, geofence, and journey internal events, are excluded. Requests targeting them return 400. See Excluded Events for the full list. All custom partner events remain eligible.
Can I undo a delete or update after it has run?
No. Operations are not reversible after execution. Validate your identifier and filters against the correct event before sending the request.
Targeting and identity
Which identifiers can I use to target a user?
Any single identifier that Insider One already knows about, such as email, phone, uuid, or a partner-defined custom identifier. Send it in the identifiers map with exactly one entry. Alternatively, send insider_id directly. Exactly one of the two must be present; they cannot be used together. If the identifier is unknown, the request returns a 400 response. No new profile is created on this path.
What if my filters match more than one event?
The request is rejected, and no change is applied. Add a more specific filter, typically a business identifier such as order_id, booking_id, or transaction_id, until the combination resolves to exactly one event. You can combine a timestamp with filters in a single request to further narrow the match.
Update behavior
Can I update multiple parameters for the same event in a single request?
Yes. List up to 50 parameters under update_params in a single request. All parameters must belong to the same event; each key must be a mapped parameter; and each value must match the parameter's data type. Parameters not listed in update_params remain unchanged.
Can I replace some parameters and remove others in the same request?
Yes. delete_null is a single request-level flag that applies to all null values in update_params. When delete_null: true, every null value removes its parameter, and every non-null value replaces its parameter, so one request can carry both replacements and removals. When delete_null: false (the default), null values overwrite the parameter with NULL instead of removing it. Non-null values always replace, regardless of this flag.
Can an update request remove a parameter completely?
Yes. Send the parameter with the value null and set delete_null: true. The parameter is removed from the event entirely. If you send null with delete_null: false (the default), the parameter is set to NULL, and it still exists on the event but holds no value.
When should I use skip_hook?
Set skip_hook: true when you want to apply a correction without re-firing the event hooks you have registered in the InOne panel. This is useful for silent historical corrections where downstream systems should not be re-notified. The per-request hook_url callback always fires regardless of this setting. On delete requests, skip_hook has no effect; delete operations do not trigger partner-registered hooks.
Outcomes and verification
How do I know if the operation succeeded?
A 202 response confirms the request was accepted and queued; it does not confirm execution. Set the hook_url field to receive the final outcome once the operation completes. The platform calls your webhook exactly once after execution with the result. If you do not receive a webhook callback, verify that your endpoint is publicly accessible and accepts POST requests from Insider One.
What happens to journeys and segments after a delete or update?
Segments and analytics are re-evaluated automatically against the corrected event data. For journeys: users currently inside a journey are not automatically removed when a past event is deleted or updated; the journey continues from their current step, and future condition steps use the corrected data. Users who have not yet entered the journey are evaluated against the current, corrected event state.
Rate limits and errors
What are the rate limits?
The delete and update endpoints share a combined limit of 250 requests per minute per account. Requests above this limit return 429 Too Many Requests. The operations export endpoint has a separate limit of 3 requests per hour per partner. These limits are fixed and apply uniformly across all accounts.
Can I request a higher rate limit?
If you need to process a high volume of corrections, spread your requests over time to stay within the 250-requests-per-minute limit.
Why am I getting a 409 response?
A 409 Conflict means another delete or update operation is currently running for the same partner, user, and event name. Wait for a short delay and retry; the conflict resolves once the in-progress operation completes.
Not finding your answer here?
See the full Create an Event Delete or Update Request reference for endpoint details, field descriptions, all response codes, and the excluded events list.