DEVELOPERS — THE API
An API that tells the truth: draft v0.
This page is a declared draft, not a final document: the event shapes as we build them today, published so your technical team reviews them early — and whatever changes before general availability, we will say, not bury.
The Seamless Enterprise API v0 is a published draft: events pushed, not polled, with one field vocabulary — event, actor, gates, lane, approval, ts — and every call against the API is written as an entry in the same register that watches everything else.
{
"event": "request.completed",
"actor": { "role": "analyst", "dept": "finance" },
"gates": { "identity": "ok", "permission": "ok",
"balance": "-1", "record": "written" },
"lane": "accuracy",
"approval": null,
"ts": "2026-06-12T12:47:09+03:00"
}Draft v0 — an illustrative entry in the shape published on the technology page; the final ships with the technical document.
DESIGN PRINCIPLES — DRAFT V0
Four principles from which the whole API reads.
The API extends the gate; it is not a back door around it: what governs conversations governs calls — identity, permission, balance, entry.
- Events, not polling. The register pushes what happened to your destinations — no polling loops guessing when to ask.
- Least privilege for tokens. A token per purpose at its narrowest scope, revocable alone without toppling the rest — and no token that opens everything.
- Explicit versioning. v0 means draft, the version travels in every payload — and a break is announced before it lands, not after it breaks.
- Every call is an entry. API calls are themselves register events — who read, what was exported, under which token.
{
"event": "approval.granted",
"actor": { "role": "finance.manager", "dept": "finance" },
"gates": { "identity": "ok", "permission": "ok",
"balance": "0", "record": "written" },
"lane": "accuracy",
"approval": { "request": "REQ-0042",
"clause": "usage-policy/export",
"scope": "single-request" },
"ts": "2026-06-12T12:46:30+03:00"
}Draft v0 — the approval carries a named role, a request id, and the policy clause it rested on.
{
"event": "export.requested",
"actor": { "role": "audit.lead", "dept": "internal-audit" },
"gates": { "identity": "ok", "permission": "ok",
"balance": "0", "record": "written" },
"lane": null,
"export": { "range": "2026-05-01..2026-05-31",
"format": "json", "destination": "siem" },
"approval": null,
"ts": "2026-06-12T12:49:18+03:00"
}Draft v0 — even an export request is a pushed event: range, format, actor; an illustrative entry.
WEBHOOKS — A DRAFT
Delivery is a declared design, not a detail left to luck.
You subscribe to the event families that matter to you — approval.* and export.*, say — and the payload reaches your endpoint as the entry is written. What follows is the draft's design posture, ahead of its final numbers.
- Retries with declared backoff. Failures retry with spaced backoff, then the delivery failure itself is recorded — no event vanishes silently. Exact cadence ships with the document.
- A signature on every delivery. Every payload is signed so your endpoint verifies its origin — by design, before it is a setting.
- Metadata, not content. The payload carries the event's facts, not the conversation text — content policy stays your organization's decision, where it belongs.
STABILITY & VERSIONING
From an honest draft to a stable contract.
The version's path is declared like everything here — four stations, no hidden fifth.
The shapes you read on this page — changeable, and declared so.
The full technical document under NDA — your team's notes feed the draft.
The document goes public, the sandbox opens, the changelog starts from its first line.
A breaking change without prior notice violates our laws — our register covers our own decisions too.
No dates published before they are commitments — our «soon» means soon.
For platform engineers: read the draft like a pull request.
Send your objections to the shapes before they freeze — one technical session whose notes actually enter the draft.
ENGINEER QUESTIONS
Asked at every draft review.
When does the API stabilize?
At general availability: today's v0 is a declared draft reviewed with the first cohort, and vNext stabilizes at launch — every breaking change before and after is announced explicitly, not discovered in your error logs.
Where is the full interactive documentation?
The full technical document is shared under NDA during evaluation and goes public at general availability. This page deliberately publishes what is honest today — the shapes and the principles — not an empty showcase console.
How are calls authenticated?
Least-privilege tokens issued from the control plane with a named scope and purpose, individually revocable — and a token's creation, revocation, and use are all register entries. Rotation and lifetime details ship with the technical document.
CONTINUE THE PATH
From the shapes to the integrations.
- Developers — the integration model on one pageHUB
- Integrations — identity, connectors, the monitoring feedSIBLING
- Observability — where these events live in the productPLATFORM
- The technology page — the first sample lives there, liveORIGIN
- The readiness checklist — identity and event items before buyingRESOURCE
- The glossary — entry, lane, and gates definedGLOSSARY
Shape the draft before it becomes a contract.
One technical session: the three shapes on a live screen, your team's objections written down in front of you — that is how an API gets built for your architecture, not ours.