Developers
A versioned REST API over the same data the app runs on, governed by the same roles — keys, webhooks, and automation, with every call isolated to your tenant and written to the audit log.
GET /v1/assets/CNV-02 Authorization: Bearer sk_live_••••4F2A { "id": "CNV-02", "name": "Conveyor 2", "site": "plant-12", "status": "out_of_service", "meter": { "run_hours": 12418, "source": "inspection" }, "open_defects": 2 }
One authorization model
The same isolation that separates tenants in the product governs every API call. A key is scoped to a role and per-key permission flags — it can never read or write beyond what that role allows. Cross-tenant access is impossible by construction, not by convention.
REST resources
A versioned /v1 JSON API over the operation's domain objects — tenant-scoped, paginated, filterable.
POST /v1/defects { "asset_id": "CNV-02-MTR", "finding": "Bearing temp 218F against 190F limit", "severity": "critical", "due_date": "2026-07-25" } 201 Created — meter snapshot captured, audit entry written
GET /v1/production?site=plant-07&period=2026-07 { "period": "2026-07", "tons": 98410, "unit": "dry_tons", "next_page": null }
Register endpoints and receive events — defect.created, inspection.failed, period.closed, storage.full — with reliable delivery: retries, a dead-letter queue for exhausted deliveries, and idempotency keys so a consumer never double-processes.
Org-scoped key management with per-key permission flags, rotation, and revocation. Rate limits are published and returned on every response — and every API call lands in the same audit trail as in-app actions.
Strata Extensions
Describe the automation; Extensions builds it over the API — with guardrails that make it safe to trust.
Every automation previews the exact change — records touched, values written — before anything goes live.
Each run is a single reviewable change, attributed in the audit log like any other write.
One control reverses a run — and an automation self-pauses with a plain-language diagnosis if something looks wrong.
Sandbox & reference
A sandbox tenant with seed data, a versioned reference, and predictable deprecation. The isolation guarantee is the same one documented on the Security page.