Create an Event Delete or Update Request

Event Delete & Update is available through three API endpoints: one to delete a single event, one to update a single event, and one to export a daily audit of all operations. This page walks through all three endpoints with authentication, field references, and request examples built around a single running scenario so you can follow the data end-to-end.

Headers

Every request to the Event Delete & Update endpoints must include the following headers.

Running scenario

Every example on this page uses the same scenario. A passenger booked a flight to Paris through your mobile app. The passenger later changed the trip to Istanbul. The booking is real, but the destination on the original event is outdated. You will see how to delete a duplicate event and how to update the booking with the corrected destination, price, and currency.

Scenario reference

• Event name: booking_completed

• Source: web

• Business identifier: booking_id: "BKG-9821"

• Parameters on the event: destination, total_price, currency, promo_code

1. Delete a single event

Use this endpoint when an event exists in the system but should not; it was fired by mistake, is a duplicate, or was a test event that landed on a real user profile. The endpoint locates exactly one matching event, removes it, and triggers automatic re-evaluation of journeys, segments, and analytics.

Endpoint

POST https://unification.useinsider.com/api/user/v1/delete-single-event

Body Parameters

Sample Request: Delete by timestamp and source

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/delete-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": {
        "email": "passenger@example.com"
    },
    "event_name": "booking_completed",
    "source": "web",
    "timestamp": "2026-03-15T10:00:02Z",
    "hook_url": "https://example.com/hooks/event-delete"
}'

How to find the source value

The source field tells Insider One which channel the event was ingested through. The values you can use are crm, web, mobile, and email:

Two ways are available to find the source for a specific event:

1. From the user profile in the InOne panel:

Open the user's profile, find the event you want to delete or update, and look at the Platform field in Event Details. Map it using the table above. For example, if the panel shows Platform: API, send "source": "crm" in your API request.

2. From a Raw Data Export:

Run a Raw Data Export from the panel for the date range that covers your event. The exported file has an src column for each event row. The value in that column is exactly what you send in the source field.

Response example:

{
  "operation_id": "f3c5e6a8-1d24-4b6f-90c1-2a5b9c8e7d44",
  "status": "accepted"
}

Sample Request: Delete by business identifier

When the exact timestamp is not available, identify the event using a business identifier in the filters field instead.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/delete-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "booking_id": "BKG-9821"
    }
  }'

Sample Responses

202 Accepted

{
  "operation_id": "f3c5e6a8-1d24-4b6f-90c1-2a5b9c8e7d44",
  "status": "accepted"
}

202 confirms acceptance, not completion.

The operation runs asynchronously. Set hook_url to receive the final outcome, success, failure, or skip, once execution completes.

Deleted events are not recoverable:

Validate your identifier and filters against the target event before sending the request. If the combination matches more than one event, the request is rejected and no change is applied. If the event does not exist, the API returns 400 with "event does not exist" and no operation record is created.

2. Update a single event

Use this endpoint when an event should remain in the system, but one or more of its parameters are outdated. The endpoint applies a PATCH-style update; only the parameters listed in update_params change. All other parameters on the event remain untouched.

Endpoint

POST https://unification.useinsider.com/api/user/v1/update-single-event

Update semantics

Update follows a PATCH model. For each key in update_params: sending a value replaces the current value; sending null either sets the parameter to NULL or removes it entirely, depending on the delete_null flag; omitting a key leaves the parameter unchanged. Event timestamps cannot be changed via update.

Understanding delete_null

delete_null is a single request-level flag that controls what happens when a parameter is sent as null in update_params. It does not affect non-null values; non-null values always replace the current value regardless of this setting.

Body Parameters

Sample Request: Replace parameter values

Correct the destination, total price, and currency on the booking event in a single call.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": {
        "email": "passenger@example.com"
    },
    "event_name": "purchase",
    "source": "web",
    "timestamp": "2026-03-15T10:00:02Z",
    "skip_hook": true,
    "update_params": {
        "unit_price": 1299.50,
        "currency": "EUR"
    }
}'

Sample Request with custom event parameters

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": { "email": "passenger@example.com" },
    "event_name": "purchase",
    "filters": {
      "custom": {
        "invoice_number": "INV12345"
      }
    },
    "update_params": {
      "custom": {
        "store_id": "store_02"
      }
    },
    "hook_url": "https://example.com/hooks/event-update"
  }'

Sample Request: Remove a parameter entirely

A promo code was attached to the booking by mistake. Set delete_null to true and send the parameter as null to remove it from the event entirely.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
        "custom": {
            "booking_id": "BKG-9821"
        }
    },
    "delete_null": true,
    "update_params": {
        "custom": {
            "promo_code": null
        }
    }
}'

Sample Request: Replace values and remove a parameter in the same call

Correct currency and total_price, and remove promo_code, in one request. With delete_null: false, non-null values are replaced, and the null value removes the parameter.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": {
        "email": "passenger@example.com"
    },
    "event_name": "booking_completed",
    "filters": {
        "custom": {
            "booking_id": "BKG-9821"
        }
    },
    "delete_null": true,
    "update_params": {
        "custom": {
            "currency": "EUR",
            "total_price": 1299.50,
            "promo_code": null
        }
    }
}'

Sample Request: Identify the event by timestamp

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": { "email": "passenger@example.com" },
    "event_name": "purchase",
    "timestamp": "2026-06-29T15:12:55Z",
    "update_params": {
      "custom": {
        "store_id": "store_02"
      }
    },
    "hook_url": "https://example.com/hooks/event-update"
  }'

Sample Responses

202 Accepted

{
  "operation_id": "a91d7c12-58f2-4d09-83c5-6f2eaa9c3b71",
  "status": "accepted"
}

Keys in update_params must be mapped event parameters.

Unmapped keys are rejected with 400. Values must match the parameter data type; type mismatches are rejected with "Data type mismatch". Event timestamps cannot be updated.

Response codes

The following response codes apply to the delete and update endpoints:

3. Update or delete array-of-objects parameters

Some event parameters hold a list of objects instead of a single value, for example, every flight leg in a booking. These are array-of-objects parameters. You cannot change them through update_params. Use object_update_params on the same update endpoint instead.

With object_update_params you can:

• Change sub-keys in one object, or in every object that matches a value.

• Delete one object, several objects, or all of them.

• Remove sub-keys from an object.

• Add new objects to the list, with or without a duplicate check.

• Replace the whole list, empty it, or remove the parameter from the event.

Endpoint

POST https://unification.useinsider.com/api/user/v1/update-single-event

The endpoint, headers, event lookup (identifiers or insider_id, event_name, timestamp or filters, source), hook_url and skip_hook work exactly as in Update a single event.

Running scenario: flight legs

The examples in this section extend the running scenario. The booking_completed event has a custom array-of-objects parameter, flight_legs, with one object per flight:

"flight_legs": [
  {
    "leg_id": "L1",
    "origin": "London",
    "destination": "Paris",
    "seat_class": "economy",
    "checkin_status": "pending"
  },
  {
    "leg_id": "L2",
    "origin": "Paris",
    "destination": "Istanbul",
    "seat_class": "economy",
    "checkin_status": "pending"
  },
  {
    "leg_id": "L3",
    "origin": "Istanbul",
    "destination": "London",
    "seat_class": "economy",
    "checkin_status": "pending"
  }
]

Body parameters

object_update_params is added next to the existing body parameters. Send update_params, object_update_params, or both.

Each parameter inside object_update_params uses one of two modes:

Custom and default parameters

Parameters are named the same way as in update_params:

You can send both kinds in the same request. In this example, flight_legs is a custom parameter, and items is a default parameter:

"object_update_params": {
  "custom": {
    "flight_legs": {
      "mode": "patch",
      "operations": [
        {
          "match": {
            "leg_id": "L2"
          },
          "set": {
            "checkin_status": "checked_in"
          }
        }
      ]
    }
  },
  "items": {
    "mode": "replace",
    "values": []
  }
}

• Send each parameter only once. The same parameter inside and outside custom is rejected.

• In your webhook result, object_update_results uses the same names you sent.

Patch operations

Each operation does exactly one thing: delete, set, unset, or append. To set some sub-keys and remove others in the same object, send two operations.

How matching works

• match lists sub-key values. An object matches when every sub-key in match has exactly that value.

• "match": {} matches every object in the parameter.

• match is required for delete, set, and unset, and not allowed with append.

• Match only on sub-keys that hold a single value (text, number, boolean, date, or URL). Values must have the sub-key's registered type, for example, a number for a number sub-key.

• If no object matches, nothing changes, and the operation still succeeds. The result in your webhook shows "matched_object_count": 0.

Matching is your responsibility. If several objects share the matched value, every one of them is changed. Match on a sub-key that is unique within the list, such as an id.

Sample Request: Update one object

The passenger checked in for the Paris to Istanbul flight and moved to business class.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": {
      "email": "passenger@example.com"
    },
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "match": {
                "leg_id": "L2"
              },
              "set": {
                "checkin_status": "checked_in",
                "seat_class": "business"
              }
            }
          ]
        }
      }
    },
    "hook_url": "https://example.com/hooks/event-update"
  }'

Only the L2 object changes. Its other sub-keys keep their values, and L1 and L3 are untouched.

Sample Request: Update every object that matches a value

Check-in opened for every flight leaving Paris. Use "match": {} instead to update every object.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "match": {
                "origin": "Paris"
              },
              "set": {
                "checkin_status": "open"
              }
            }
          ]
        }
      }
    }
  }'

Sample Request: Delete objects

The return flight was canceled, and the first leg was added by mistake. Several operations can go in one request.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "match": {
                "leg_id": "L3"
              },
              "delete": true
            },
            {
              "match": {
                "leg_id": "L1"
              },
              "delete": true
            }
          ]
        }
      }
    }
  }'

flight_legs now holds only the L2 object.

Sample Request: Remove sub-keys from an object

The seat class on the first leg was sent by mistake.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "match": {
                "leg_id": "L1"
              },
              "unset": ["seat_class"]
            }
          ]
        }
      }
    }
  }'

Add objects

append adds objects to the end of the list.

• Without unique_by, every request adds the objects again. Sending the same request twice adds them twice.

• With unique_by, Insider One first looks for an existing object with the same values for those sub-keys. on_conflict decides what happens when one is found:

  • skip (default): the new object is not added.

  • update: the existing object is updated with the new object's sub-keys.

We recommend sending unique_by so a retried request does not create duplicates.

Sample Request: Add a flight, or update it if it already exists

The passenger added a connecting flight. If L4 is already on the event, it is updated instead of added again.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "append": [
                {
                  "leg_id": "L4",
                  "origin": "London",
                  "destination": "Dublin",
                  "seat_class": "economy",
                  "checkin_status": "pending"
                }
              ],
              "unique_by": ["leg_id"],
              "on_conflict": "update"
            }
          ]
        }
      }
    }
  }'

Sample Request: Replace the whole list

The booking changed completely, and you have the full new list of flights. Objects not in values are removed; nothing is merged.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "insider_id": "iid-12345",
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "replace",
          "values": [
            {
              "leg_id": "L1",
              "origin": "London",
              "destination": "Istanbul",
              "seat_class": "business",
              "checkin_status": "pending"
            },
            {
              "leg_id": "L2",
              "origin": "Istanbul",
              "destination": "London",
              "seat_class": "business",
              "checkin_status": "pending"
            }
          ]
        }
      }
    }
  }'

To empty the list and keep the parameter, send "values": [].

To clear the parameter, send "values": null. As with update_params, delete_null decides the result: true removes the parameter from the event, false (default) sets it to NULL.

Sample Request: Update regular and array-of-objects parameters together

The Istanbul-to-London leg was refunded: the total price drops and the leg is removed. Both changes apply together, or neither does.

curl --location --request POST 'https://unification.useinsider.com/api/user/v1/update-single-event' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --data-raw '{
    "identifiers": {
      "email": "passenger@example.com"
    },
    "event_name": "booking_completed",
    "filters": {
      "custom": {
        "booking_id": "BKG-9821"
      }
    },
    "skip_hook": true,
    "update_params": {
      "custom": {
        "total_price": 899.00
      }
    },
    "object_update_params": {
      "custom": {
        "flight_legs": {
          "mode": "patch",
          "operations": [
            {
              "match": {
                "leg_id": "L3"
              },
              "delete": true
            }
          ]
        }
      }
    },
    "hook_url": "https://example.com/hooks/event-update"
  }'

Sample Responses

202 Accepted

{
  "operation_id": "a91d7c12-58f2-4d09-83c5-6f2eaa9c3b71",
  "status": "accepted"
}

As with other updates, 202 confirms the request was accepted, not that it was applied.

Result in your webhook

When the update succeeds, the result sent to your hook_url includes object_update_results. It shows, for each parameter and each operation, how many objects were affected. For the request in Update one object:

{
  "operation_id": "a91d7c12-58f2-4d09-83c5-6f2eaa9c3b71",
  "operation_type": "update",
  "status": "success",
  "insider_id": "iid-12345",
  "object_update_results": {
    "flight_legs": {
      "mode": "patch",
      "object_count": 3,
      "operations": [
        {
          "matched_object_count": 1,
          "updated_object_count": 1
        }
      ]
    }
  }
}

If the update fails, object_update_results is not sent, and nothing on the event changes.

Errors

• Rejected with 400 when you send the request.

The message names the parameter, for example, object_update_params.custom.flight_legs: ....

• Failed after acceptance (reported to your webhook).

The update is not applied.

Things to know

• No new sub-keys. Every sub-key you send must already be registered on the parameter, with the right type.

• Object limit. A parameter holds up to its configured maximum number of objects (50 by default). An update can shrink a list that is over the limit, but cannot grow it.

• Up to 50 operations per parameter, and up to 50 parameters per request across update_params and object_update_params.

• All or nothing. If any part of the request fails, no change is applied, including changes in update_params.

• Deleting the whole event still works with Delete a single event, including events that have array-of-objects parameters.

4. Export operations history

Use this endpoint to retrieve a daily audit of every delete and update operation that ran for your account on a given calendar day. The request is accepted synchronously and returns a request_id immediately. The export file and a summary are delivered asynchronously to your webhook URL once ready.

Endpoint

POST https://unification.useinsider.com/api/raw/v1/event-operations-export

Body Parameters

Sample Request

To export all successful update operations for 15 March 2026:

curl --location --request POST 'https://unification.useinsider.com/api/raw/v1/event-operations-export' \
  --header 'X-PARTNER-NAME: mybrand' \
  --header 'X-REQUEST-TOKEN: 1a2b3c4e5d6f' \
  --header 'Content-Type: application/json' \
  --body '{
    "date": "2026-06-30",
    "hook_url": "https://example.com/hooks/ops-export"
}'

Sample Responses

Sync response

202 Accepted

{
  "request_id": "9d4b2a6e-1f3c-4f2d-8d5e-7b9c0a1234ef"
}

Async webhook payload: Success

Once the export is ready, Insider One POSTs the following to your hook_url. The download URL is a time-limited signed link and expires in 24 hours, so download the file promptly.

{
  "request_id": "9d4b2a6e-1f3c-4f2d-8d5e-7b9c0a1234ef",
  "partner": "mybrand",
  "status": "success",
  "url": "https://insider-exports.s3.amazonaws.com/...signed-url...",
  "date": "2026-03-15",
  "operation_type": "update",
  "summary": {
    "total_operations": 1284,
    "delete_count": 0,
    "update_count": 1284,
    "success_count": 1271,
    "failed_count": 13
  }
}

Async webhook payload: Export failure

{
  "request_id": "9d4b2a6e-1f3c-4f2d-8d5e-7b9c0a1234dk",
  "partner": "mybrand",
  "status": "failed",
  "message": "internal error generating export"
}

Sync error codes

Rate limit for this endpoint is separate.

The operations export endpoint allows 3 requests per hour. This is independent of the 250 requests per minute limit shared across the delete and update endpoints.

Limitations

• API only. There is no panel interface for delete or update in this version.

• One event, one user per request. Each request targets exactly one event on one user profile. Bulk operations are not supported.

• One event type per request. To correct more than one event type, send separate requests.

• Filter and parameter limits. Up to 50 entries in filters and up to 50 entries in update_params per request.

• Timestamps are immutable. Event timestamps cannot be changed via update.

• Operations are not reversible. Validate filters before sending.

• Rate limit. 250 requests per minute per partner, shared across delete and update. The export endpoint has a separate limit of 3 requests per hour.

• Payload size. Up to 5 MB per request.

• Identifier resolution is read-only. If the identifier is unknown, the request returns a 400 response. No new user profile is created on this path.

• Excluded events cannot be targeted. See the Excluded Events section below.

Excluded events

Some events are managed directly by the Insider One platform, and they reflect message delivery, session state, and other operational signals that must remain consistent for Architect, segmentation, and analytics to function correctly. These events cannot be deleted or updated through the API. Requests targeting them return HTTP 400 with the message "excluded by platform integrity policy".

The entire misc source is also blocked. Every event under misc is rejected, regardless of the event name.

All custom events, anything not listed in the table below, remain eligible for delete and update.