← Back to all docs

Spotnana API

Spotnana is a Travel-as-a-Service platform that connects travel buyers, sellers, and providers on a single modern infrastructure for corporate and leisure travel. Its API-first, open platform exposes REST APIs for trips, air, hotel, car, and rail search and booking, plus user, company, policy, payment, and document management—and webhooks for travel events. Supergood layers a resilient, normalized API and managed authentication on top so you integrate once and stay in sync as Spotnana evolves.

By Alex KlarfeldMay 30, 2026
Spotnana API

What is Spotnana?

Spotnana is a Travel-as-a-Service (TaaS) platform that connects travel buyers, sellers, and providers on a single modern technology infrastructure. Built on a cloud-based, microservices, API-first architecture, Spotnana powers corporate and leisure travel programs for TMCs, technology companies, financial services firms, and travel agencies—with customers including Brex, Marriott, Lufthansa, and SAS. Its open platform exposes the same APIs and embeddable UI components that Spotnana's own products are built on.

Core platform components include:

  • Content Engine (aggregates, dedupes, and normalizes air, hotel, car, and rail content, including NDC)
  • Booking Engine (microservices automating workflows like self-service flight changes, exchanges, and cancellations)
  • System of Record (transaction data, trips, and analytics)
  • Agent Desktop and embeddable out-of-the-box UI components with white-labeling and turn-key SSO
  • Open APIs and software integrations across expense, HR, payments, duty of care, and sustainability

Common data entities:

  • Trips, Bookings, PNRs, Itineraries
  • Air, Hotel, Car, and Rail search results and reservations
  • Users/Travelers, Companies/Organizations, and Travel Policies
  • Payments, Payment Sources, and Invoices
  • Events, Event Templates, and Documents

The Spotnana Integration Challenge

Spotnana ships a genuinely API-first, well-documented developer platform—but wiring it into production travel automation still involves real friction:

  • Partner onboarding gates: clientId/clientSecret credentials are issued per channel partner, so access requires a partner relationship and environment provisioning before any calls
  • Token and session management: OAuth-style access tokens must be refreshed and rotated, and headless automation has to handle expiry cleanly
  • Async booking workflows: air, hotel, car, and rail search and book are multi-step and stateful, with exchanges and cancellations spanning several calls and events
  • Content normalization: aggregated GDS, NDC, and direct-connect content varies by supplier, so downstream systems must reconcile heterogeneous fare and rate shapes
  • Webhook delivery and reconciliation: travel events fire asynchronously and must be deduped and matched back to trips and PNRs reliably
  • Policy and approval logic: company-specific travel policies, approval chains, and entitlements shape what a given user can book and see

How Supergood Creates Spotnana APIs

Supergood layers a resilient, normalized API and managed authentication on top of Spotnana's open platform—handling credential issuance, token lifecycle, and event reconciliation so you integrate once and stay in sync as Spotnana evolves.

  • Manages clientId/clientSecret credentials and OAuth-style access tokens with automatic refresh and rotation
  • Orchestrates multi-step air, hotel, car, and rail search-and-book workflows, including exchanges and cancellations
  • Normalizes responses across Trip, Air, Hotel, Car, User, Company, Policy, and Payment objects so you integrate once and rely on consistent shapes
  • Ingests and dedupes Spotnana webhooks, matching travel events back to trips and PNRs

Use Spotnana with AI agents: Spotnana MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your Spotnana partner setup, environments, and the travel workflows you want to automate.

  • Supergood Generates and Validates Your API

We deliver a production-ready Spotnana adapter with managed auth and normalized trip, booking, and traveler objects.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Spotnana's APIs and content sources evolve.

spotnana

API Endpoints

Authentication

POST/authenticate

Authenticate with clientId/clientSecret and obtain an OAuth-style access token for downstream calls.

Trips

GET/trips

List and retrieve trips, itineraries, and PNRs with filters for traveler, company, status, and date range.

Air

POST/air/search

Search air content across GDS, NDC, and direct-connect sources for a given route, dates, and travelers.

Air

POST/air/book

Book a selected air offer, creating a reservation and adding it to the traveler's trip.

Hotel

POST/hotel/search

Search hotel availability and rates by location, dates, and policy, returning normalized rate options.

User Management

GET/users

Retrieve users/travelers, their company associations, profiles, and applicable travel policies.

Use Cases

Sync trips and bookings into your data warehouse

- Pull trips, itineraries, and PNRs across air, hotel, car, and rail into a single warehouse - Stream booking, exchange, and cancellation events to downstream BI and finance tools - Reconcile traveler and company records for unified travel reporting

Automate corporate travel booking workflows

- Run air, hotel, car, and rail search-and-book flows programmatically against policy - Apply company travel policies, approval chains, and entitlements per traveler - Trigger self-service changes, exchanges, and cancellations without agent clicks

Connect travel spend to expense and finance

- Push trip and payment data into expense management and accounting systems - Match invoices and payment sources back to bookings and travelers - Surface out-of-policy and pending-approval spend to finance workflows

Keep traveler and company data in sync

- Provision users, companies, and policies from HR and identity systems - Pull profiles, loyalty programs, and policy assignments for downstream tools - React to webhook events when travelers, companies, or policies change

Technical Specifications

Authentication

clientId/clientSecret with OAuth-style access tokens, handled in a managed session

Connectivity

Spotnana's open REST APIs across Trip, Air, Hotel, Car, User, Company, Policy, and Payment resources

Response format

Normalized JSON across trips, bookings, travelers, and payment objects

Rate limits

Adaptive throttling tuned to your partner allocation to avoid platform-side limits

Session management

Automatic token refresh, credential rotation, and expiry handling

Data freshness

Near real-time pulls for trips, bookings, and content with optional scheduled syncs

Security

Encrypted credential vault, scoped access tokens, and audit logging

Webhooks

Event subscriptions for booking, exchange, cancellation, and trip status changes

Latency

Sub-second reads on cached entities; multi-second waits on async air and hotel search-and-book

Throughput

Horizontally scaled workers sized to multi-content-source search and booking volume

Reliability

Retry, backoff, and idempotency keys for bookings, exchanges, and cancellations

Adaptation

Continuous monitoring of Spotnana API releases, content source changes, and webhook schema drift

Frequently asked questions

Yes—Spotnana is genuinely API-first with a documented developer portal. Supergood adds a managed authentication and normalization layer on top so you handle credentials, token lifecycle, async booking workflows, and webhook reconciliation once, rather than building and maintaining that plumbing yourself.

API access uses clientId/clientSecret credentials issued per channel partner, so a partner relationship and environment provisioning are required. Supergood works against your existing partner credentials and entitlements.

Air, hotel, car, and rail search and booking are covered, including post-booking exchanges and cancellations, with content aggregated across GDS, NDC, and direct-connect sources and normalized into consistent objects.

Supergood ingests Spotnana webhooks for booking, exchange, cancellation, and trip status changes, dedupes them, and matches each event back to its trip and PNR so downstream systems stay consistent.

Yes. Trips, payments, and traveler records are exposed through the same normalized API, so you can sync to expense, accounting, and HR systems—Spotnana itself integrates with tools like Brex, Expensify, Workday, and Stripe.

Ready to get a real API?