API Service Status Codes
Overview
This is a list of HTTP status codes returned from the API. If you use an API client library, refer to the error handling section of the particular client library documentation to learn how to receive the status code.
If you are troubleshooting an issue, you can enable logging of conversion details with the setDebugLog() API method. When enabled, the logs are available in your conversion log.
Status Codes
| Code | Message | Description |
|---|---|---|
| 200 | OK ¶ | The API call succeeded. |
| 400 | Bad Request ¶ | The user sent an invalid request. |
| 401 | No Authorization Provided ¶ | Authentication is required and has failed or has not yet been provided or your license does not exist. |
| 403 | Service Suspended ¶ | Your license is suspended or there are no credits left. |
| 405 | Method Not Allowed ¶ | The method specified in the request is not allowed. The request method must be POST. |
| 413 | Request Entity Too Large ¶ | The size limit for the uploaded data is 50MB. You can zip your HTML to avoid this error. |
| 429 | Too Many Requests ¶ | The user has sent too many requests in a given amount of time (rate limiting). |
| 430 | Concurrent Requests Exceeded ¶ | The limit of max concurrent requests was exceeded. |
| 452 | No Input Specified ¶ | There is nothing specified to be converted. |
| 453 | Unknown Conversion Option ¶ | Some conversion option is unknown. See details in HTTP response body. |
| 454 | Too Complex Input ¶ | The input is too complex or large. It can't be converted. Try to simplify your input data. |
| 455 | Conversion System Error ¶ | The conversion can't be finished due to a system error. |
| 456 | Wrong Input File ¶ | The input file is not specified correctly. Files are accepted only in multipart POST requests. |
| 457 | Unknown File Type ¶ | The type of the input file is unknown. The file has no extension. |
| 458 | Conversion Time Exceeded ¶ | The request was aborted because it took long time. A typical cause of this error is too many images in the HTML page which take too long to download. Another cause might be a long running JavaScript. Try to simplify your input data or speed up the page load time. |
| 459 | Bad Archive ¶ | The archive uploaded can't be accepted. It's too large, corrupted or contains symbolic links. |
| 460 | Too Large Output ¶ | The output is too large. Try to simplify your input data or compress images. |
| 470 | Invalid Value ¶ | A conversion option is set to an invalid value. |
| 471 | Navigation Failed ¶ | The converted URL can't be navigated to. |
| 472 | Sub-requests Number Exceeded ¶ | Exceeded the maximum number of sub-requests during a conversion. |
| 473 | Main Frame Error ¶ | The main frame loaded with an HTTP code >= 400. |
| 474 | URL Load Error ¶ | The URL loaded with an HTTP code >= 400. |
| 475 | Custom JavaScript Time Exceeded ¶ | The request was aborted because the custom JavaScript took long time. |
| 476 | Element Not Found ¶ | The element specified for print or wait was not found in the input document. |
| 477 | Unsupported Document Type ¶ | The input document type is unknown or not supported. For example, the HTML content type should be text/html. |
| 478 | Hostname Not Resolved ¶ | The URL hostname could not be resolved. |
| 479 | Invalid URL ¶ | The URL is invalid. |
| 480 | Invalid SSL Certificate ¶ | The converter couldn't establish an HTTPS connection because of an invalid SSL certificate. |
| 481 | SSL Error ¶ | There was a problem connecting to Pdfcrowd servers over HTTPS. This could be caused by several reasons, one of them is that your local CA certificate store is out of date or not configured correctly. An alternative is to use the API over HTTP. The HTTP mode can be enabled by the setUseHttp method.
|
| 502 | Bad Gateway ¶ | The 502 status code indicates a temporary network issue. Try the request again. |