01
Versioned contracts
Explicit versions and controlled compatibility rules for public integration surfaces.
Developer platform
Connect the system without bypassing the controls.
Integration architecture follows versioned contracts, scoped access, idempotent commands, business events and traceable changes.
01
API principles
An integration is another governed participant in the operation.
The final public production API will be documented only when the released services and support model are ready.
02
Scoped access
Tenant, organisation, role and permission boundaries remain active for integrations.
03
Business events
Approved systems react to meaningful lifecycle events through retryable delivery.
04
Governed records
Integrations use validated application contracts instead of direct database access.
02
Contract direction
Readable requests. Explicit context. Deterministic outcomes.
The interface should make tenant scope, idempotency and business intent visible in every request.
Illustrative contract · not a final public endpoint
POST /api/v1/crm/opportunities
Authorization: Bearer <integration-token>
Idempotency-Key: <unique-request-id>
Content-Type: application/json
{
"organizationId": "org_001",
"companyId": "company_001",
"name": "North region rollout"
}- REST resource contracts
- Outbound webhooks
- Import and migration tools
- Shared SDK and generated types
- Audit and idempotency support
- Provider fail-closed behaviour
Integration discovery
Start with the business event—not the connector logo.
Describe the source system, destination, data ownership, trigger, retry behaviour and evidence required after the exchange.