Live betaCloudflare edge · OpenAPI 3.1

Build travel workflows on Tripistic.

A focused REST surface for tours, availability, bookings and operations. The same domain model as the Tripistic app, with workspace-scoped keys, stable envelopes and safe retries.

Scoped keys

Workspace-level credentials

Safe writes

Idempotent booking creation

Event-ready

Webhook workflows in beta

Quickstart

Make your first read in under a minute.

Create a scoped key in Settings → API keys, store it server-side, then call the live tours endpoint.

bash
curl -sS "https://api.tripistic.com/v1/tours?limit=20" \
+  -H "Authorization: Bearer $TRIPISTIC_API_KEY"

Reference

Live endpoints

The catalog below mirrors the current beta Worker surface. Expand an operation for scope, filters and a copyable request.

12 of 12 operations

Create a booking with an idempotency key so retries cannot double-book a guest.

Scope: bookings:write
cURL
curl -X POST https://api.tripistic.com/v1/bookings \
+  -H "Authorization: Bearer $TRIPISTIC_API_KEY" \
+  -H "Content-Type: application/json" \
+  -H "Idempotency-Key: 4f8c2a1e-9d33-4a11-b2c7-77c9a1e0f2b4"

Response shape

Success responses use data + meta.requestId. Errors use error.code, message, optional details and requestId.

Pagination

Cursors are opaque. limit defaults to 25 and is capped at 100; persist nextCursor until hasMore is false.

Retries

Retry 429 and 5xx with exponential backoff. Re-read availability before retrying a 409 capacity conflict.

Money and IDs

Money is integer minor units with an ISO currency. Treat prefixed IDs as opaque strings.

Build the next travel workflow on Tripistic.

Launch direct bookings, operations, CRM, itinerary drafting, and enterprise controls from one modern platform.