RapidAPI Support
Uptime check API support for RapidAPI users
Help for developers using the PingAlert uptime check API through RapidAPI. Run the first checks below, then contact PingAlert with the listed details if the problem continues.
Already have a PingAlert account? Log in
At a glance
- 01Include the requestId from the response
- 02HTTP 429 means you hit the rate limit
- 03HTTP 504 with TIMEOUT means the target was too slow
- 04Contact PingAlert at pingalert.io/contact
First checks
- Send the same request from the RapidAPI console to rule out problems in your own code.
- Check the HTTP status: 429 means you hit the rate limit, and 504 with errorCode TIMEOUT means the target did not respond in time.
- Confirm the request includes url, and that timeoutSeconds (1 to 30) and expectedStatusCode (100 to 599) are in range.
- Questions about your subscription, plan or key go to RapidAPI. Questions about check results go to PingAlert.
What to include in a support request
- The requestId from the response
- Timestamp of the failing request
- The request body you sent, with secrets removed
- The errorCode and errorMessage, or a screenshot from the RapidAPI console
Where to get help
RapidAPI
For subscriptions, plans and API keys, start from the PingAlert listing on RapidAPI .
PingAlert support
For check results and API behavior, contact PingAlert at pingalert.io/contact.
Continuous monitoring
Need scheduled checks, alerting, incidents or status pages? Create a PingAlert account.
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.