The full set of response codes from the PDF.co API are as follows:

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