As 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:
- CUSTOM (if the user is subscribed to a custom plan.)
The version of the proxy
The IP address of the client making the request. It could be shown in a comma-separated format like "126.96.36.199, 188.8.131.52" where the first IP address belongs to the client and any subsequent IP represents a proxy.
Users consuming your API on RapidAPI 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. This will reset each day or each month, depending on how the API pricing plan is configured.
Note that x-ratelimit-requests-remaining is different than x-ratelimit-remaining.
x-ratelimit-remaining is related to the rate limit of the API. Therefore, this header will only appear in APIs with a rate limit.
The x-ratelimit-reset header will let you know when the rate limit will reset (typically days or hours).
This header is set to true when the RapidAPI proxy generates the response, (i.e. the response is not generated from the provider)
Updated about a month ago