Operator API
Everything an operator can do in the panel, as a versioned JSON API over HTTP for scripts, tooling and other systems, independent of the operator pages, which stay as they are. An API is a permanent contract: the auth model, error envelope, versioning and idempotency are chosen deliberately before the surface grows. This is the contract for a programmatic caller; the integration contract is the one for a plug-in, and the two are not conflated.
Phases: API design and auth model (JSON over HTTP with an OpenAPI description; token or client-credentials; error envelope; pagination and idempotency; whether responses carry hypermedia links; a health route only, to validate); catalog endpoints (organization types, products with their payment-provider mapping, capability sets with rules, plan ladders with tier reordering); runtime endpoints (persons, organizations, grants, the per-organization composite); billing and integrations (read-only over the payment mirror; integration endpoints); OpenAPI publication with a first generated client used by the demo seeder; API audit, per-principal rate limits, cross-origin lockdown.
No results
Try adjusting your search filters.