Link Search Menu Expand Document response links are broken

After 15 June 2022 to improve the security of the platform, output links will become much longer by default. New links are longer but provide additional layer of the security.

Please review the information below to make sure that your app or integration will continue to run properly after this change:

Note: If you use Zapier, Integromat, UiPath or another plugin then in most cases you won’t notice this change.

Old - highly randomized output link (with encrypt=false, up to 150 characters in most cases):


New - highly randomized and signed output link (2,000+ chars length, equal to encrypt=true):


You can test new long links by setting encrypt parameter to true in your app or script. New long links are similar to having encrypt parameter always set to true.

Why we need to change this?

  • Signed links provide additional layer of protection, new embedded signatures for links are powered by SHA 256-bit algorithm and Amazon AWS powered security mechanism for links expiration;
  • Expiration for output links can be controlled more precisely up to 1 minute (for example, you can set expiration=1 to expire output link in just 1 minute);

Following are the other common reasons for broken output links.

By default response links are accessible for 1 hour. After that duration, the file is removed from cloud and links are expired.

However, one can adjust expiration parameters on request as per requirement.

Async Job is created and it’s success status is not checked

All requests can be executed in asynchronous mode by setting async parameter value to true. This asynchronous request returns a jobId as well as an output URL in response.

Now, This URL won’t be ready and publicly accessible unless the job is checked by job/check request and it has success status.

API response does not pass through JSON parser/decoder

Most of the request clients have a built-in JSON parser/decoder. For security reasons, response by-default contains the encrypted file url link this.

    "url": "",

For most scenarios, this URL will be accessible without issue as it’ll be through JSON parser/decoder.

However, when a request is made by clients which does not have built-in JSON parser/decoder (example cURL), it’ll show a raw response and the user might be confused with a link appearing as broken.

For example, a cURL response would be like the following.


Please notice the character ‘\u0026’ in response. Normally after JSON decoding this would be replaced with ‘&’. Now, cURL does not have a built-in JSON parser/decoder and it shows raw responses.If this un-parsed raw link is directly utilized it’ll appear as broken.

Use “name” parameter to get custom filename

name parameter works on most of API endpoints that return files in output.

For example, pdf/edit/add API endpoint by default returns the filename of the original file, You can modify filename by adding name parameter in request e.g "name": "filename_here",.

Response Body:

    "hash": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
    "url": "",
    "pageCount": 1,
    "error": false,
    "status": 200,
    "name": "filename_here",
    "credits": 21,
    "duration": 277