Response Codes#
The full set of response codes from the PDF.co API are as follows:
Code |
Description |
---|---|
|
Success. |
|
No content. The server successfully processed the request, and is not returning any content. |
|
Bad request. Typically happens because of bad input parameters, or because the input URLs can’t be reached, possibly due to access restrictions like needing a login or password. |
|
Unauthorized. Authentication is required and has failed or has not yet been provided. |
|
Not enough credits. |
|
Access forbidden for input URL. |
|
The requested resource could not be found. |
|
The server timed out waiting for the request. |
|
The URI provided was too long for the server to process. |
|
The request entity has a media type which the server or resource does not support. |
|
The user has sent too many requests in a given amount of time (see: rate limiting). |
|
Invalid Password. Password protected document. |
|
Input document is damaged or of incorrect type. |
|
Permissions. The operation is prohibited by document security settings. You can turn off this check by setting the |
|
Profiles parsing error. Please make sure that the configuration is supported. Explore profiles samples at |
|
Timeout error. To process large documents or files please use asynchronous mode (set the |
|
Some files required for conversion are missing. |
|
Invalid template. |
|
Invalid URL or HTML. Make sure that provided URL is valid and accessible. |
|
Invalid index range. Page index is out of range. Get page count via /pdf/info endpoint. First page is |
|
Invalid page range specified. |
|
Invalid URL. |
|
Invalid parameters. |
|
Failed to send email. |
|
Invalid color. Should be a valid color. For example: "Red" , "Green" or Html HexString like "#CCBBAA" or without ‘#’ symbol as "CCBBAA". |
|
SMTP server blocked. |
|
Invalid base64 image. |
|
Incorrect result data. |
|
Something went wrong. Please try again or contact customer support. |
|
Not implemented. The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
|
Bad gateway. The server was acting as a gateway or proxy and received an invalid response from the upstream server. |
|
Service unavailable. The server cannot handle the request because it is overloaded or down for maintenance. |
|
Gateway timeout. The server was acting as a gateway or proxy and did not receive a timely response from the upstream server. |
|
HTTP version not supported. The server does not support the HTTP version used in the request. |