Status codes

When interacting with the Movies API, you may encounter various HTTP status codes in the responses. These status codes convey important information about the outcome of your API requests. Here's a guide to the most common status codes you might encounter:

200 OK 😃

• Description: The request was successful, and the server has returned the requested data.

201 Created 🚀

• Description: The request to create a resource (e.g., adding a new movie review) was successful. The server has created the resource, and the response will typically include information about the newly created resource.

204 No Content 📭

• Description: The request was successful, but there is no data to return in the response. This is often used for successful DELETE requests where the resource has been removed.

400 Bad Request 🤨

• Description: The server couldn't understand the request, possibly due to invalid parameters or missing data in the request payload. Check your request and ensure it conforms to the API's requirements.

401 Unauthorized 🙅‍♂️

• Description: Authentication is required, and either the provided API key is missing or invalid. You need to authenticate to access the requested resource.

403 Forbidden 🚫

• Description: The request is understood, but it's not permitted. This could be due to insufficient permissions associated with your API key.

404 Not Found 🕵️‍♂️

• Description: The requested resource does not exist on the server. Double-check your request URL and parameters to ensure they are correct.

429 Too Many Requests ⏳

• Description: You've exceeded the rate limit for your API key. Review the Request Limits section to understand rate limiting policies and how to avoid this error.

500 Internal Server Error 🤯

• Description: An unexpected error occurred on the server while processing your request. This is usually not something you can fix on your end. Report the issue to our support team.

503 Service Unavailable 🛠️

• Description: The server is temporarily unavailable, often due to maintenance or high server load. You can retry your request after some time.