Correct an ingested event
This API lets you to correct events. Available in both synchronous and asynchronous mode
- Usages: Reduction of all usages associated with this event
- Revenue: Reduction of all revenues associated with this event
- Entitlements: Entitlements(Feature Credits) consumed by this event are granted back to the account.
Possible Actions:
- UNDO: Undo all usages, revenue and entitlements associated with an event
- REDO: Performs UNDO and re-ingests the same event
- REDO_EVENT: Performs UNDO and re-ingests the correction payload of the event
Query Parameters: Allowed filter combinations
- Sync mode: Maximum of first 30 events matching the filters with the default sort order being EVENT_SOURCE_TIME DESC, EVENT_ID ASC can be corrected in a single request.
- Async mode: When query parameter async = true is given, events matching the filters will be considered for correction and takes place in background.
Status of background job can be obtained using List Jobs API
Query Parameters
Query Parameters
Unique identifier of the account corresponding to the event
Unique identifier of an event generated by Togai for reference
Identifier of an event provided by the user
Timestamp of an event provided by the user
Timestamp corresponding to the event ingestion time in Togai
Determines the mode of the correction. Defaults to false
Allowed Combinations
Allowed Combinations
account_id
account_id
, id
account_id
, event_id
account_id
, event_source_time
account_id
, event_id
, created_at
account_id
, event_id
, event_source_time
Authorizations
Bearer authentication header of the form Bearer <token>
, where <token>
is your auth token.
Query Parameters
Action to perform in event correction
UNDO
, REDO
, REDO_EVENT
"UNDO"
Specifies whether to start a migration only after a confirmation
false
Body
Event Correction Payload for event correction
Response
Success response
Events Correction response