Glossary
Response Codes
The full set of response codes from the PDF.co API are as follows:
Code | Description |
---|---|
200 | Success. |
204 | No content. The server successfully processed the request, and is not returning any content. |
400 | Bad request. Typically due to bad input parameters or unreachable input URLs (e.g., access restrictions like login or password). |
401 | Unauthorized. Authentication is required and has failed or has not yet been provided. |
402 | Not enough credits. |
403 | Access forbidden for input URL. |
404 | The requested resource could not be found. |
408 | The server timed out waiting for the request. |
414 | The URI provided was too long for the server to process. |
415 | The request entity has a media type not supported by the server or resource. |
429 | Too many requests in a given time period (see: rate limiting). |
441 | Invalid Password. Password protected document. |
442 | Input document is damaged or of incorrect type. |
443 | Permissions. The operation is prohibited by document security settings. You can turn off this check by setting the profiles param to {CheckPermissions: false} . Important: only use this if you are the owner or have legal permission. |
444 | Profiles parsing error. Please ensure that the configuration is supported. See /profiles samples. |
445 | Timeout error. For large documents, use asynchronous mode (async=true ) and check status via /job/check . For many-page files, use the pages parameter. |
446 | Some files required for conversion are missing. |
447 | Invalid template. |
448 | Invalid URL or HTML. Ensure the provided URL is valid and accessible. |
449 | Invalid index range. Page index is out of range. Use /pdf/info to get page count. First page is 0 . |
450 | Invalid page range specified. |
452 | Invalid URL. |
454 | Invalid parameters. |
455 | Failed to send email. |
456 | Invalid color. Should be a valid name (e.g., “Red”) or hex string (e.g., “#CCBBAA” or “CCBBAA”). |
457 | SMTP server blocked. |
466 | Invalid base64 image. |
490 | Incorrect result data. |
500 | Something went wrong. Please try again or contact support. |
501 | Not implemented. The server was acting as a gateway or proxy and received an invalid response. |
502 | Bad gateway. The server was acting as a gateway or proxy and received an invalid response. |
503 | Service unavailable. Server is overloaded or under maintenance. |
504 | Gateway timeout. Server didn’t get a timely response from upstream. |
505 | HTTP version not supported. |