Didit Event Monitoring API

Overview

Events are everything your platform knows besides money movement: the login before a withdrawal, the poker hand that moved chips between two accounts, the bonus claimed twice, the chargeback a week later. Every category uses one envelope, every event is idempotent on your event_id, and events are evaluated by the same rule engine as transactions (rules opt in with scope.record_types).

Key facts:

• Opt-in. Turn it on in the Business Console under Transactions > Settings > Event monitoring. Until then every write (POST /v3/events/, /v3/events/batch/, /v3/events/sdk-token/, /v1/events/, /v1/events/batch/) returns 403 with "code": "event_monitoring_disabled" and nothing is stored. Reads are unaffected.
• Two lanes, same records and rules. Server lane /v3/events/ with x-api-key; device lane /v1/events/ with an X-Monitoring-Token minted by your backend (no API key in the browser or app).
• Synchronous verdict. The response carries status and score. Correlation rules and sequences longer than 24h run within minutes (correlation_pending: true), then update the event in place.
• Same subject as transactions. subject.vendor_data resolves to the same user (or business) record your KYC sessions and transactions use.
• No webhooks fire for events: read the response or the list endpoints.
• Money movement itself goes to POST /v3/transactions/ (see the didit-transaction-monitoring skill).

Pricing: No list price is published for events; check didit.me/pricing.

Guides: https://docs.didit.me/transaction-monitoring/events | https://docs.didit.me/transaction-monitoring/sdk-event-submission | https://docs.didit.me/transaction-monitoring/event-rules | https://docs.didit.me/transaction-monitoring/rules-library