Tenant scope
Every request belongs to an organisation context. Data access is never global by default.
Developer Docs / API
A structured introduction to the SimplyOS API surface.
This public documentation describes the integration model without publishing private credentials, internal endpoints or environment secrets.
Core concepts
Authentication
API access belongs inside the same identity and permission model as the rest of SimplyOS.
Customer APIs
Customer systems can integrate without receiving unrestricted tenant access.
Booking resources
Integrations can create or exchange booking and shipment information.
Events
Webhook patterns can publish operational changes to connected systems.
Tracking
External carrier updates can return through push or polling patterns.
Auditability
API activity can be retained as part of the platform's traceable activity model.
Versioning
Integration contracts should be versioned so changes do not silently break connected systems.
Rate controls
API usage belongs under tenant and platform governance rather than unlimited anonymous access.
Before production integration
Implementation note
The supplied website source pack describes API capability and governance, but it does not contain a publishable endpoint catalogue, authentication URL, public base URL, SDK package or production credential flow. Those details should be generated from the deployed API contract before this page is used as executable reference documentation.