Skip to main content

PDF.co response links are broken or not working

Updated over a month ago

Starting June 15, 2022, PDF.co updated its output link format to enhance security. Output links are now much longer (2000+ characters) and use signed URLs by default.

These new links work automatically in most platforms like Zapier, Make, UiPath, etc. You may only notice an issue if your app or integration:

  • Has a URL length limit

  • Doesn’t support long URLs

  • Parses URLs incorrectly

Why the links changed

New output links use:

  • Signed URLs powered by Amazon AWS

  • SHA-256 encryption

  • Link expiration control (up to the minute)

This adds an extra layer of security and ensures links expire safely.

Example of old vs. new link:

What to do

If your app breaks due to long URLs:

  1. Check if URL parsing or storage limits are causing truncation.

  2. Test using encrypt=false (for short links). → Only for non-sensitive files.

  3. Update your integration to support long URLs (recommended).

  4. If using code/scripts → make sure your string handling supports 2000+ characters.

You can manually test the long link behavior by setting encrypt=true in your API call.

Did this answer your question?