Guide

HTTP Status Codes

Happy Endpoint APIs follow standard REST conventions. Use these status codes to build robust, automated data workflows that handle success and failure gracefully.

Response Reference

CodeStatusAction
200OKThe request was successful and the data is in the response body. If the search yielded no results, you will still get a 200 with an empty data array.
400Bad RequestA required parameter is missing, has an invalid value, or the request body is malformed. Check the endpoint reference for required fields and correct formats.
401UnauthorizedThe X-RapidAPI-Key header is missing or the key is invalid. Verify the key in your RapidAPI dashboard and ensure it is sent in the request headers.
403ForbiddenYour key is valid but does not have access to this endpoint. Check that your RapidAPI subscription is active and covers the endpoint you are calling.
404Not FoundThe requested resource or endpoint path does not exist. Check the URL, path parameters, and that you are calling the correct API host.
429Rate LimitYou have exceeded your plan's rate limit. Implement exponential backoff and retry after the window resets, or upgrade to a higher tier on RapidAPI.
500Internal Server ErrorAn unexpected error occurred on our side. These are rare and transient. Retry with backoff. If the error persists, contact support.
503Service UnavailableThe upstream data source is temporarily unavailable. Retry after a short delay. Monitor the RapidAPI status page if the issue continues.