Supported URL sources, TLS requirements, request size limits, and the cache prefix option for reusable file inputs in PDF.co API calls.
Supported File Sources
The API supports TLS 1.2 and 1.3 for secure connections. Earlier versions such as TLS 1.0 and 1.1 are deprecated and should be avoided.
Tip: For re-usable files (e.g., PDF templates), use cache: before the URL
(e.g., cache:https://example.com/file1.pdf) to reduce repeated downloads and avoid
errors like Access Denied or Too Many Requests. It stores a local copy of the file after the first download, so it does not need to be fetched again from the original server.
The PDF.co API supports publicly accessible links from any source, including Google Drive, Dropbox, and PDF.co Built-In Files Storage.File inputs are accepted only via URLs and not through direct uploads. If your file is stored locally or not publicly accessible, you must upload it using the
File Upload endpoints to get a publicly accessible URL.Each input file supplied through the url parameter must be 100 MB or smaller. Request-body and upload limits are separate.For data security, you have the option to encrypt output files and decrypt input files.
Learn more about user-controlled data encryption.
PDF.co Request size
API request payloads must not exceed 4 MB. This limit applies to the request body, not the source file downloaded through the url parameter. Each source file supplied through url has a separate 100 MB input limit.
Was this page helpful?
Assistant
Responses are generated using AI and may contain mistakes.