Developers
Send events. Get outcomes.
Zentra is designed to be driven by events. This page shows the intended developer experience. Examples are illustrative and not connected to a live service.
01The loop, in code
Event JSON → Zentra → workflow → action.
{
"type": "reconciliation.mismatch",
"source": "payments-gw",
"occurred_at": "2026-03-04T08:32:11Z",
"entity": {
"kind": "settlement_batch",
"id": "B-2291"
},
"data": {
"ledger_total": 118450,
"gateway_total": 118195,
"currency": "INR"
}
}- Ingest
- Signal
- Context and policy
- reconciliation.mismatch → wf_recon_mismatch
- assign investigation (review)
- verify totals
Example data
02Interactive example
Send an example event. Watch it process.
curl -X POST https://YOUR_ZENTRA_HOST/api/v1/events \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Idempotency-Key: evt-2026-03-04-0001" \
-d '{"type":"reconciliation.mismatch","source":"payments-gw","occurred_at":"2026-03-04T08:32:11Z","entity":{"kind":"settlement_batch","id":"B-2291"},"data":{"ledger_total":118450,"gateway_total":118195,"currency":"INR"}}'- Receiving event…
- Enriching context…
- Evaluating policy…
- Preparing workflow…
// Response appears here after you send the example event.
03Building blocks
What you will build with.
Event ingestion
POST an event with a type, source, timestamp and entity. Use an idempotency key so retries are safe.
Webhooks
Receive events from systems that can call a URL. Outbound webhooks notify you of signals and outcomes.
Workflow triggers
Trigger workflows by event type, signal condition, schedule, or manually.
Authentication
Scoped API keys bound to a workspace. Keys are shown once and can be rotated or revoked.
Logs
Request, event and run logs with replay, so you can see what Zentra received and did.
Documentation
Concepts, guides and reference, using the same object model as the product.
Sample data is used throughout this site.