RapidAPI Documentation

Welcome to the RapidAPI docs. You'll find comprehensive guides and documentation to help you start working with RapidAPI as quickly as possible, as well as support if you get stuck. Let's jump right in!

Get Started    Guides

Headers Sent by API Proxy

Headers sent as response

When consuming an API on RapidAPI, you will always receive the following headers appended to the response:

The current version of the API proxy used by RapidAPI.

The number of requests the plan you are currently subscribed to allows you to make, before incurring overages.

The number of requests remaining before you reach the limit of requests your application is allowed to make, before experiencing overage charges.

The time remaining to reset the current billing cycle in seconds

This header is set to true when the RapidAPI proxy generates the response, (i.e. the response is not generated from the provider)

Headers sent to your API servers

If you are an API provider, you will receive some additional headers appended in the request to your servers:

This is a secret unique key for every API that is appended by the proxy on every request. For high security, you can validate this secret server-side and check if it equals the key shown in the API Admin (under the Network Settings tab at market.mashape.com).

The username of the user that's making the request.

The name of the subscription (if any). The values can be:

  • PRO
  • MEGA

The version of the proxy

The IP address of the client making the request. It could be shown in a comma-separated format like "," where the first IP address belongs to the client and any subsequent IP represents a proxy.

Updated 3 months ago

Headers Sent by API Proxy

Suggested Edits are limited on API Reference Pages

You can only suggest edits to Markdown body content, but not to the API spec.