Your Panion data, in your own systems.

The Partner API lets tour operators pull their bookings, the daily manifest from every channel, their sales and their analytics (how each tour sells on every site and channel) into their own tools. It also covers a few narrow actions: checking guests in and sending a guest a link to pay the balance they owe.

It is for operators with an Oracle account. Team owners and admins create API keys in Oracle under Settings, API keys, and choose what each key may read or do.

Quickstart

1. Create a key
In Oracle, open Settings, API keys. Owners and admins pick the scopes the key needs. The key is shown once.

2. Make your first call

curl https://www.panion.travel/api/v1/me \
  -H "Authorization: Bearer pnn_live_..."

3. Explore the docs
Every endpoint with its fields, examples and errors, in the reference or as Markdown for your agent.

Documentation

API reference: Every endpoint, interactive.
llms.txt: A short overview for AI agents.
llms-full.txt: The complete reference as Markdown.
OpenAPI 3.1: For code generators and tools.
Changelog: What changed, newest first.

The API never creates bookings

Bookings are made through Panion checkout or your own booking system. No endpoint reserves, books or rebooks. Every key sees only its own operators' data; the one exception is analytics for a site your operator owns, which cover every tour sold there.