Skip to main content
POST
Correct an ingested event

Query Parameters: Allowed filter combinations

All matching events will be considered for correction
  • 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
string
required
Unique identifier of the account corresponding to the event
string
Unique identifier of an event generated by Togai for reference
string
Identifier of an event provided by the user
string
Timestamp of an event provided by the user
string
Timestamp corresponding to the event ingestion time in Togai
boolean
Determines the mode of the correction. Defaults to false
account_idaccount_id, idaccount_id, event_idaccount_id, event_source_timeaccount_id, event_id, created_ataccount_id, event_id, event_source_time

Authorizations

Authorization
string
header
required

Bearer authentication header of the form Bearer <token>, where <token> is your auth token.

Query Parameters

action
enum<string>
required

Action to perform in event correction

Available options:
UNDO,
REDO,
REDO_EVENT
Example:

"UNDO"

require_confirmation
boolean

Specifies whether to start a migration only after a confirmation

Example:

false

Body

application/json

Event Correction Payload for event correction

event
object

Contents of the event

Response

Success response

Events Correction response

data
object[]
required
Required array length: 1 - 50 elements