​

How to Limit Source File Access to Approved Users Only

You need to ensure that only approved users can access your source PDF files—especially when passing them into PDF.Co API endpoints.

​

Why This Happens

When using PDF.co, you might need to share a PDF file as a link, but want to ensure that it’s only accessible to authorized users or systems. This is especially important when dealing with sensitive or private documents.

​

How to Secure File Access

To securely provide files to PDF.co endpoints while limiting access:

​

Option 1: Use a Protected URL

• Store the PDF file on your own server.
• Use HTTP authentication (username/password) or generate a one-time-use link.
• Then, pass that protected link as the file input into PDF.Co API endpoints.

Learn more in the PDF.co API documentation.

​

Option 2: Upload the File to PDF.co Securely

When uploading your file to PDF.co:

• It’s stored temporarily under a highly randomized name, making it hard to guess.
• Enable the encrypt parameter to encrypt the file at rest.
• The link is also signed with a unique token, acting like a password.

Encryption Documentation

​

Automatic File Deletion

To further control file access:

• Files are automatically removed after 1 hour by default.

​

Helpful Tips

• Use the encrypt parameter for an extra layer of security at rest.
• For extra control, manage access using signed URLs or password-protected file servers.

​

Still Need Help? Contact Support

To help us assist you faster, please include:

• What you’re trying to do
• Your platform (API, Zapier, Make, etc.)
• Any input files, URLs, or sample data
• The exact error message (if applicable)
• A screenshot or short explanation of what went wrong