The API Report CardAPI Index
Spotnana

Spotnana API

Travel & Expense · spotnana.com

Spotnana runs an unusually open developer portal at developer.spotnana.com with OpenAPI-published REST APIs across air, hotel, trips, policy, users, and payments, using OAuth 2.0 client credentials. Credentials still require a partner relationship: an account manager provisions them.

Last verified: July 2026Hospitality & Travel
API GRADE
D+
VERIFIED JUL 2026

SCORECARD

ExistenceGOODOpenAPI-published REST APIs at developer.spotnana.com span the full travel stack, browsable without a login.
AccessPOORNo self-serve signup: a Spotnana account manager provisions clientId and clientSecret after a partner relationship is in place.
CoverageGOODAPIs cover air, hotel, trips, policy, users, company, payments, and documents; outbound webhooks lag the inbound REST surface.
AuthGOODOAuth 2.0 client credentials with short-lived bearer tokens and refresh tokens; the token endpoint's limit is documented.
Docs & DXGOODOpenAPI published specs, concept docs, workflow guides, and changelog are browsable without login at developer.spotnana.com.
StabilityMIXEDBookings inherit upstream GDS and NDC supplier outages, and PNR field shapes vary by source, so downstream code handles each.
MORE FROM THE REPORT CARD
Supergood: Spotnana has an API, but using it means gates, contracts, or workarounds. Ours doesn't: stable endpoints, normalized JSON, managed auth.

Frequently asked questions

Spotnana scores D+ on the API Report Card. Spotnana runs an unusually open developer portal at developer.spotnana.com with OpenAPI-published REST APIs across air, hotel, trips, policy, users, and payments, using OAuth 2.0 client credentials. Credentials still require a partner relationship: an account manager provisions them.

Tried to integrate with Spotnana?
SOURCES
Partner relationship required before clientId/clientSecret is provisioned - not pure self-serve developer signup like Stripe or Plaid spotnana.com
Public rate limit guidance is thin - only the get-auth-token endpoint has a documented 100-calls-per-5-minutes limit; other endpoint limits are not openly published spotnana.freshdesk.com
Bookings depend on a heterogeneous upstream supplier mix (Sabre, Amadeus, Travelport GDS plus 20+ NDC direct connects plus OTAs plus hotel CRSs) - when a single supplier degrades, the Spotnana API surface reports incidents downstream (e.g. May 2026 Sabre Air shopping outage) status.spotnana.com
Event APIs use chained workflows for internal orchestration, but a fully-documented outbound webhook layer for partner systems (booking-created, ticket-issued, refund-completed events to partner URLs) is less mature than the inbound REST surface developer.spotnana.com
Authentication uses two long-lived secrets (clientId + clientSecret) plus short-lived bearer tokens plus refresh tokens - partners must implement credential rotation, token refresh, and 401-retry logic carefully spotnana.freshdesk.com
Multi-source content normalization means returned PNR / itinerary data has fields that vary by supplier - partners must handle Sabre-format PNRs, NDC-format orders, and LCC direct-booking confirmations differently in downstream code spotnana.com
Sandbox parity with production is partial - certain supplier connections (e.g. live NDC direct connects, hotel CRSs) are not always testable end-to-end in sandbox, surfacing edge cases only after production go-live spotnana.com
Status page incidents in 2026 show repeated dependency on Sabre's API health (May 21, May 22 Singapore POS) - integrators need to subscribe to status.spotnana.com to attribute outages correctly to Spotnana vs. upstream supplier status.spotnana.com
Capacity planning is opaque - partners onboarding high-volume corporate accounts must coordinate with Spotnana's solutions team rather than reading published per-tier quota tables spotnana.freshdesk.com
Document Management API surfaces partner-owned itinerary PDFs and supplier-generated invoices but format and completeness varies by supplier and channel - partners often supplement with browser-rendered PDFs developer.spotnana.com
Customer support quality is mixed - users report delays in agent response and inconsistent resolution quality g2.com
Booking fees are charged on transactions and refunds can be hard to recover, leading to user frustration on cancelled trips g2.com
Mobile/desktop app crashes when filters are pushed hard or users iterate quickly on flight/hotel options g2.com
Rates shown in search occasionally need to be re-verified with the agent or supplier; users report mismatch between search price and final ticketed fare g2.com
Inventory completeness is dependent on upstream content suppliers - certain long-haul, multi-stop, or niche-LCC fares unavailable g2.com
End-user-facing UX is largely driven by the partner (Brex, Marriott, CWT) rather than Spotnana, so issues are difficult to escalate cleanly between layers spotnana.com
May 2026 platform incident: guest-user trip search failures caused by upstream Sabre Air shopping API outage (downstream supplier dependency) status.spotnana.com
Singapore point-of-sale Sabre Air shopping failures (May 21, 2026) affecting Spotnana direct customers status.spotnana.com
Capterra reviewers cite a learning curve when partner TMCs migrate travelers off legacy OBTs (Concur Travel, GetThere, Sabre Red) onto the Spotnana stack capterra.com
Some reviewers note thin reporting/analytics depth versus legacy enterprise platforms like Concur, particularly for multi-entity / multi-currency rollups g2.com