Migration guide
Learn how to migrate from RapidAPI
Migration Guide: Moving from RapidAPI to new Platform
Overview
This guide outlines the necessary steps to migrate from RapidAPI to our new API platform. The migration primarily involves changes to the request URL and authentication headers. The response payload format remains unchanged, ensuring a seamless transition with no required modifications to response handling.
Migrating from RapidAPI to the new platform requires some changes on how you request endpoints. However, the response payload remains unchanged, so no modifications to response handling are necessary.
Changes
What Has Changed?
API Base URL Update
Old Base URL:
New Base URL:
Authentication Header Change
Old Header:
New Header:
Host Header Removal
RapidAPI required the X-RapidAPI-Host
header, but our new platform does not require this header. Simply remove it from your requests.
Migration Steps
Updating Your Requests
Old Request Format
New Request Format
Additional Considerations
Rate Limits: Ensure that your new API key has the appropriate rate limits for your usage.
Testing: Before fully switching, test your integration using the new API key to confirm that requests function as expected.
Deprecation Timeline: If RapidAPI access is being phased out, check the deprecation schedule and transition before the cutoff date to avoid service disruptions.
Need Help?
Last updated