Integrations

Documented boundaries before integration claims.

The platform is intended to connect cleanly with the systems an operator already uses. Phase 1 publishes a preview contract; it does not expose a live sandbox or production API.

Preview — subject to change

Sales channels

Potential connections for structured enquiries and bookings, subject to a proven channel contract.

Supplier systems

Potential availability and confirmation workflows where a reliable supplier interface exists.

Messaging and support

Conversation references and operational handoffs without claiming a channel is live today.

Finance and reporting

Export and reconciliation boundaries designed to keep booking and settlement facts traceable.

Static API contract preview

A predictable booking object

Illustrative response from the local OpenAPI preview. It does not call api.savinlabs.com or sandbox-api.savinlabs.com.

Read the docs
{
  "id": "bkg_preview_01",
  "status": "supplier_pending",
  "service_date": "2026-10-18",
  "party": { "adults": 4, "children": 1 },
  "next_action": "confirm_supplier"
}

Integration principles

Explicit status

Failures and pending work must remain visible rather than being flattened into “synced”.

Idempotent writes

Future write operations are expected to tolerate safe retries and preserve source references.

Narrow credentials

Future API access will be scoped to the minimum data and actions needed for an approved integration.

Have a specific integration in mind?

Send the workflow and interface you need. We will separate what can be piloted from what still needs product work.

Get API access