Preview documentation. These pages describe the intended Zentra interfaces. The API is not live, and endpoints, fields and behaviour may change before release.

Documentation

Zentra turns business events into signals, adds context, decides what should happen, runs the workflow and verifies the outcome.

Signal

Context

Action

Outcome

Core objects

Object	Meaning	Example ID
Event	A raw fact from a system	evt_7Q2K9
Signal	An event or pattern that matters	sig_0412
Case	A tracked issue with owner and SLA	CASE-2081
Workflow	A reusable response definition	wf_recon_mismatch
Run	One execution of a workflow	run_88213
Policy	A rule that bounds automation	pol_approval_limit

Quickstart

Create a workspace. Workspaces isolate events, keys and configuration.
Create an API key. Scope it to events:write.
Send an event. See the request under Events.
Watch the signal. If the event matches a rule, a signal appears with context.

Events

An event describes something that happened in a system. Send a type, a source, when it occurred, the entity involved, and data.

POST /api/v1/events
Authorization: Bearer YOUR_API_KEY
Idempotency-Key: evt-2026-03-04-0001

{
  "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"
  }
}

202 Accepted
{
  "id": "evt_7Q2K9",
  "status": "accepted",
  "signal": {
    "id": "sig_0412",
    "priority": "high",
    "reason": "amount delta above threshold and SLA under 4h"
  },
  "context": {
    "related_records": 17
  },
  "workflow": {
    "id": "wf_recon_mismatch",
    "run": "run_88213",
    "mode": "review"
  }
}

Signals

A signal is an event, or a pattern of events, that meets a condition. Signals have a priority, an SLA clock and an owner.

id: sig_0412
priority: critical, high, medium, low
state: new, acknowledged, workflow_running, resolved
context: related records, history, similar incidents

Workflows

A workflow runs five steps: trigger, context, decision, action and verification. Policies decide whether a step runs automatically, needs review, or is blocked.

workflow: wf_recon_mismatch
trigger: signal.type == "reconciliation.mismatch"
context:  fetch related records by batch
decision: policy approval_limit -> mode review
action:   assign investigation to Finance Ops
verify:   ledger_total == gateway_total

API

The API is designed as JSON over HTTPS with predictable resource names.

Method	Path	Purpose
POST	/api/v1/events	Send an event
GET	/api/v1/signals	List signals
GET	/api/v1/signals/{id}	Read a signal with context
POST	/api/v1/workflows/{id}/runs	Start a run
GET	/api/v1/runs/{id}	Read run state and outcome

Draft interface

Webhooks

Inbound webhooks send events to Zentra. Outbound webhooks notify your systems of signals and outcomes. Deliveries are logged and retried.

{
  "type": "signal.resolved",
  "signal": "sig_0412",
  "run": "run_88213",
  "outcome": "verified",
  "elapsed_seconds": 462
}

Authentication

API keys are bound to a workspace and scoped to actions. A key is shown once at creation. Rotate or revoke keys at any time.

Header: Authorization: Bearer YOUR_API_KEY
Scopes: events:write, signals:read, workflows:run
Rotation: Create a new key, switch, revoke the old key

Integrations

Connect systems through webhooks, the API, or connectors when available. See the integration architecture. For a system you need, tell us.