Global Parameters
Each Happy Endpoint API has its own endpoints and parameters, but authentication and request conventions are consistent across the documentation. Use the API reference for endpoint-specific fields and this guide for shared request patterns.
Required RapidAPI headers
X-RapidAPI-Key
Your RapidAPI application key. Keep this value secret and send requests from a backend service, worker, serverless function, or secure server environment.
X-RapidAPI-Host
The API-specific host value shown on the RapidAPI listing. Host values can differ between APIs, so copy the value from the exact API you are integrating.
Query and path conventions
Use the API reference as the contract
Parameters vary by API and endpoint. Check the Scalar reference for required fields, accepted values, response examples, and path structure before building a request.
URL-encode query values
Encode search terms, locations, category names, product URLs, and other query values. This avoids malformed requests when values contain spaces, symbols, or non-ASCII characters.
Keep secrets out of URLs
Send authentication through headers rather than query strings. URLs are often stored in logs, browser history, analytics tools, and monitoring systems.