Skip to main content
Monitoring starts the moment your first event lands. In the next five minutes you create a key, send one payment.succeeded event, and read it back to confirm Reconify stored it.

1. Get an API key

Your organization’s keys live in Dashboard → Settings → API Keys. A write key covers this quickstart, and Authentication covers the scopes in full.

2. Install an SDK

The API is plain JSON over HTTPS, so cURL needs no installation. The official SDKs add typed requests, structured errors, and cursor helpers.

3. Send one event

An event carries the flow it belongs to, its type, the reference that identifies the operation, and the entity the money is moving toward. Monetary event types also carry an amount and a currency.
The response carries one result per submitted event, in the order you sent them:
An accepted result means Reconify stored the event as evidence. It says nothing yet about whether the operation passed evaluation.
Reconify has no sandbox. Every event you send here becomes real evidence in the organization behind your key, so a throwaway reference such as order-123 keeps your first test out of production data.

4. Read it back

A read or admin key confirms what arrived. The cURL examples across these guides read it from RECONIFY_READ_KEY:
The record comes back with a processing status. received means Reconify holds the durable receipt, published means the event entered asynchronous processing, and processed means evaluation finished. Evaluation runs in seconds, so a first read often shows received.

What comes next

The next two pages turn one event into a monitored flow.

Send events

Batches, item results, and safe retries.

Monitoring model

Flows, operations, deadlines, and findings.