Developers

Build on the travel operating system.

A predictable REST API over the same domain model the product uses — bookings, availability, customers, operations, and itineraries.

Quickstart

Issue a key in Settings → API keys, then make your first authenticated request.

curl https://tripistic.com/api/workspaces/$WORKSPACE_ID/bookings \
  -H "Authorization: Bearer $TRIPISTIC_API_KEY" \
  -H "Content-Type: application/json"

Scoped credentials

Tokens inherit the role they were issued under and are bound to one workspace. Cross-tenant access is impossible, not merely discouraged.

Signed webhooks

Every delivery carries an HMAC-SHA256 signature and timestamp, with a six-attempt retry schedule and replayable delivery log.

OpenAPI 3.1

Generate a typed client in any language, spin up a mock server, or run contract tests against the published specification.

Idempotent writes

Send an Idempotency-Key on creating requests. Retries return the original result instead of duplicating a booking.

Reference

Support for builders

Planning a migration, an OTA bridge, or a high-volume import? Tell us before you start — we can advise on sequencing and, on enterprise plans, arrange temporary elevated rate limits.

Ship your integration on a platform that treats the API as a first-class surface.

Launch direct bookings, operations, CRM, AI itineraries, and enterprise controls from one modern platform.