Expedia Group Rapid API vs ETG API (RateHawk)

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.

ETG API (RateHawk)

Hotel search and booking are documented in a public Swagger 2.0 file, an llms.txt index and a changelog with 64 dated entries in 2026. Access is by contract. Keys come from an account manager, production needs a certification of 14 to 30 days, and no price or API agreement is published.

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

ETG API (RateHawk)

1. Call /api/b2b/v3/overview/ first. It lists the endpoints the key may use and each one's request limit.
2. Keep sandbox IDs, keys and hashes inside api-sandbox.ratehawk.com. Sandbox region IDs are limited to 2011, 2395, 2734 and 6053839.
3. Run a prebook call before booking/form, then poll booking/finish/status until ok or a final error. Treat timeout, unknown and 5xx as still in progress.
4. Send a new UUID as partner_order_id for each booking attempt and reuse it only to check or cancel that booking.
5. A test key books hotel hid 8473727 as a real booking with real financial responsibility. Cancel it afterwards.