LiteAPI (Nuitee Connect) vs Travelport TripServices APIs

LiteAPI (Nuitee Connect)

Sandbox key at sign-up, same base URL as production, no card. Hosted MCP's documented setup puts the API key in the URL query string and exposes 111 generated tools.

Travelport TripServices APIs

Public OpenAPI 3.0 files, Markdown docs and an llms.txt cover search, pricing, booking, ticketing, exchanges and hotel stays, with dated release notes through August 2026. Production needs a sales contract and certification with 15 days' notice. No price, API rate limit, status page or SLA is published, and the terms bar automated tools without written permission.

LiteAPI (Nuitee Connect)

1. Use /hotels/rates with a short hotelIds list from /data/hotels; a broad rates call is slow and large
2. Always prebook before book and read the cancellation policy in the prebook response, since refundability differs per rate
3. Send a unique clientReference on book; a repeat returns error 4005 instead of a second booking
4. Set margin explicitly on every rates call. Zero means net rates with no commission to you
5. Send the key to the MCP in an X-Api-Key header rather than ?apiKey= where the client allows it

Travelport TripServices APIs

1. Request one token and cache it for 24 hours. Travelport declines certification for refreshing more often than every 23 hours without a stated reason
2. Send Accept-Encoding: gzip, deflate and XAUTH_TRAVELPORT_ACCESSGROUP (or TVP-PCC-CORE) on every call. Production traffic without compression is refused
3. Send offersPerPage on a journey-based search, or later calls can't reference its results. Cached searches last 12 minutes for GDS content and 34 for NDC
4. Commit a workbench within 30 minutes or it expires, and read Result/Error in the body even on HTTP 200
5. Get written authorisation for agent access before production. The terms bar automated tools and speculative or duplicate bookings