RapidAPI Security
Uptime check API security on RapidAPI
How to protect your RapidAPI key and what RapidAPI and PingAlert each handle when you call the uptime check API. For developers taking the API into production.
Already have a PingAlert account? Log in
At a glance
- 01Keep RapidAPI keys server-side
- 02Authentication and plans managed by RapidAPI
- 03Rate limited, with HTTP 429 responses
- 04Timeouts return HTTP 504 with errorCode TIMEOUT
Key handling
- Keep your RapidAPI key in a backend service, CI secret store or server-side environment variable.
- Do not put the key in browser or mobile client code.
- Rotate your key in RapidAPI if you suspect it has been exposed.
Who handles what
- RapidAPI manages authentication, the API host and headers, and your plan.
- PingAlert runs the uptime check you request and returns the result.
- The RapidAPI console has the current request examples and plan pricing.
Using the API safely
Rate limits
Requests are rate limited. Handle HTTP 429 responses in your code by waiting before you retry.
Timeouts
Set timeoutSeconds from 1 to 30, default 30. A check that times out returns HTTP 504 with errorCode TIMEOUT.
Certificates and redirects
Use verifySsl and followRedirects to match how the endpoint you are checking is meant to behave.
Two ways to use PingAlert
Run on-demand checks through RapidAPI, or monitor around the clock with a PingAlert account.
Subscribe on RapidAPI to call the uptime check API from your own code. Create a PingAlert account when you need continuous monitoring, alerting, incidents, status pages and client workspaces.
PingAlert uptime check API, available on RapidAPI.