Submit monitoring events
Durably acknowledge one event or a batch of 1–500 flow-monitoring events. Each event is validated independently; accepted and rejected indexes are returned together.
Authorizations
Organization API key. Use a write-scoped key for event ingestion.
Body
- Option 1 · object
- Option 2 · object[]
- Option 3 · object
Submit one event, a bare array of events, or the backward-compatible events wrapper.
Target identifier. Its entity type is derived from the selected flow.
1Monitoring flow that defines the expected evidence sequence.
payment_to_wallet, payment_to_order, wallet_to_wallet, wallet_to_payout Stable local business reference supplied by the producer.
1Lifecycle event type, such as payment.succeeded.
order.fulfilled, payment.failed, payment.initiated, payment.succeeded, payout.failed, payout.initiated, payout.succeeded, wallet.credited, wallet.debited, wallet.refunded Decimal amount in the event currency.
^(0|[1-9][0-9]*)(\.[0-9]+)?$Optional opaque identifier for the single earlier event that caused this event. It is not resolved at ingest.
1 - 200^[\x21-\x7E]+$Optional producer-supplied opaque identifier propagated across services. Do not include secrets or personal data.
1 - 200^[\x21-\x7E]+$Three-letter uppercase ISO currency code.
^[A-Z]{3}$Optional provider, failure, or retry context.
Optional stable ULID used to identify the event across retries.
^evt_[0-9A-Z]{26}$Optional flat key-value context retained with the event.
Time when the event occurred in the source system.
Response
Accepted
Results in the same order as the submitted events.