Kaptio Journeys API

The order engine behind Kaptio Journeys. One trip per customer journey; purchase orders from every channel sold into it; payments allocated to order lines and passengers; groups, block requests and mass changes on the same records. Every capability is a documented HTTP API, and the screens Kaptio ships call the same API your integration does.

Overview

The resource model: trips, quotations, purchase orders, order lines, payments, groups and the orchestration configuration that routes each line to the system that executes it.

End-to-end example

Quote, convert, add an excursion order from the mobile app, take payments, cancel the add-on and refund. Every request and response on the page was captured from the service.

Fundamentals

Authentication, environments, versioning, idempotency keys, optimistic concurrency, errors and request ids, pagination and rate limits.

Events

The outbox the order engine publishes, the inbound status events specialist systems send, and the event catalogue that maps them to statuses.

API reference

Every operation with its request schema, captured examples and error codes, generated from the service's contract. Also available as an OpenAPI 3.0 document.

Availability

What the API provides today and what it does not, stated plainly, so an integration design never depends on a capability that is not there.