Expedia Group Rapid API vs LiteAPI (Nuitee Connect)

Expedia Group Rapid API

Expedia's lodging inventory with shop, price check, book, change and cancel in one API. Partner application and site review before production, no self-serve keys.

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.

Expedia Group Rapid API

1. Build the SHA-512 signature from key, secret and the current epoch seconds in that order, per request
2. Send Customer-Ip and the session headers the docs ask for, since fraud checks use them
3. Point everything at test.ean.com until the site review is through; the paths match api.ean.com
4. Follow the links in each response rather than building URLs; price check and book links carry tokens
5. Read the Rate-Limit-Minute-Remaining and Rate-Limit-Day-Remaining headers, since the docs publish no ceilings

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