rapidapi / compatibility
The marketplace path stays intact.
RapidAPI remains supported for existing integrations, marketplace billing, and teams that already distribute keys through the platform. New direct customers should start with the first-party API.
transport
RapidAPI headers
Keep the subscription key and host header server-side. The endpoint paths and response shapes remain compatible.
curl https://timelogic-api-world-time-timezones-time-calculations.p.rapidapi.com/v1/time/current?tz=Europe/Paris
-H X-RapidAPI-Key: YOUR_KEY
-H X-RapidAPI-Host: timelogic-api-world-time-timezones-time-calculations.p.rapidapi.comDirect and RapidAPI are not competing contracts.
The direct API is the primary customer path with first-party key management. RapidAPI remains a compatible transport with its own billing and account model.