Developers
Build on the travel operating system.
A predictable beta REST API over the same domain model the product uses — bookings, availability, customers, operations, and tours.
Quickstart
The public API is in beta: resource reads and booking creation are callable today with an API key from Settings → API keys. The expanded contract remains subject to beta changes.
# BETA — create a booking with an API key.
curl -X POST https://api.tripistic.com/v1/bookings \
-H "Authorization: Bearer $TRIPISTIC_API_KEY" \
-H "Content-Type: application/json"Scoped credentials
Scoped API keys are live in Settings → API keys (hashed, shown once, revocable). They authenticate the beta public resource routes today.
API Worker (beta)
api.tripistic.com is live on Cloudflare's edge, serving health, version, the OpenAPI 3.1 contract, and beta tours, availability, bookings, customers, departures, guides and vehicles routes.
Signed webhooks (beta)
Workspace owners can register endpoints, select events, rotate encrypted secrets and replay deliveries. Each delivery carries an HMAC-SHA256 signature and timestamp.
OpenAPI 3.1 (live beta)
The deployed Worker publishes the beta contract for the callable /v1 surface. The full workspace design remains separately documented.
Idempotent writes (beta)
Booking creation accepts an Idempotency-Key header so 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 now and, on enterprise plans, discuss elevated rate limits for when the public API ships.