Link Search Menu Expand Document response links are broken

Following are the 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.