Getting Started
Error codes & Rate limits
Below is a list of errors you may come across while using TMDB
Status Codes
Codes | Status Codes | Description |
---|---|---|
1 | 200 | Success. |
2 | 501 | Invalid service: this service does not exist. |
3 | 401 | Authentication failed: You do not have permissions to access the service. |
4 | 405 | Invalid format: This service doesn’t exist in that format. |
5 | 422 | Invalid parameters: Your request parameters are incorrect. |
6 | 404 | Invalid id: The pre-requisite id is invalid or not found. |
7 | 401 | Invalid API key: You must be granted a valid key. |
8 | 403 | Duplicate entry: The data you tried to submit already exists. |
9 | 503 | Service offline: This service is temporarily offline, try again later. |
10 | 401 | Suspended API key: Access to your account has been suspended, contact TMDB. |
11 | 403 | Duplicate entry: The data you tried to submit already exists. |
12 | 503 | Service offline: This service is temporarily offline, try again later. |
13 | 401 | Suspended API key: Access to your account has been suspended, contact TMDB. |
14 | 500 | Internal error: Something went wrong, contact TMDB. |
15 | 201 | The item/record was updated successfully. |
16 | 401 | Device denied. |
17 | 401 | Session denied. |
18 | 400 | Validation failed. |
19 | 406 | Invalid accept header. |
20 | 422 | Invalid date range: Should be a range no longer than 14 days. |
Rate Limits
Legacy rate limits
As of December 16, 2019, we have disabled the original API rate limiting (40 requests every 10 seconds.) If you have any questions about this, please head over to our API support forum.
While our legacy rate limits have been disabled for some time, we do still have some upper limits to help mitigate needlessly high bulk scraping. They sit somewhere in the 50 requests per second range. This limit could change at any time so be respectful of the service we have built and respect the 429 if you receive one.