GET signingUrls returns 404 on existing agreement

Question

The goal is to create an agreement and then get its signing urls by using the AdobeSign API.

So first, the steps to reproduce:

1. Create an agreement

2. Use the id returned from the create agreement call to fetch the signing urls

3. 404 Not found

Whenever i wait for one or more seconds, I get a valid 200 response containing the urls.

Is there another way to avoid the 404? As a fallback right now, I use an exponential backoff as not to do 30 calls before getting a valid response.

Kind regards

Jan_Ae · Accepted Answer

Found in the Documentation

The creation and update APIs are now asynchronous, which significantly improves their response time. This frees clients from waiting on these operations and they can move on to next steps in their workflow.

Clients should now poll on the status of the newly created resource before certain sub-resource operations, such as documents in the case of agreements.

cherisanerd · Answer

Or you could put a delay in before asking for the signing URL. Depending on number of pages in the document and merging of fields, rendering of the agreement can take a number of seconds.

The goal is to create an agreement and then get its signing urls by using the AdobeSign API.

Sign up

To post, reply, or follow discussions, please sign in with your Adobe ID.

Sign in to Adobe Community

To post, reply, or follow discussions, please sign in with your Adobe ID.

Scanning file for viruses.

This file cannot be downloaded