Highlighted

Multiple agreement ids for the same document

New Here ,
Aug 17, 2018

Copy link to clipboard

Copied

Hi,

I am trying to integrate our app with Adobe Sign API and I noticed some weird behaviour when getting information about agreements.

When I call URL, with setting x-api-user header to Andy

https://api.na2.echosign.com:443/api/rest/v5/agreements/3AAABLblqZhC2Z-XZwtMvTIaa047IkmWALZ6O1rcSXwh...​​

I get Agreement with different agreementId then I used in URL (3AAABLblqZhAZKGFOdJqlN13TKCD4NOCLBVYUmWBC8Fu8M5sNdAcjQLZxtvojWImO5Ri9xfJtxtKT81cbfzyrAepxroQ7Jfvi)

Also it's getting more weird:

- after Access token refresh if I call the same URL first with x-api-user set to Matyas and then Andy I get an agreement with correct agreementId (same as in URL) in both cases.

- if, after Access token refresh, I call this URL with x-api-user header set to Andy and then Matyas I get an agreement with wrong agreementId in both cases

It is always the same agreement and the only difference in both responses is agreementId and latestVersionId. Since I need to download information about agreements for multiple users, I am getting duplicate records in our database with different Ids.

This is very frustrating... Is it a bug? Or am I missing something?

Thanks for your reply.

Views

82

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Multiple agreement ids for the same document

New Here ,
Aug 17, 2018

Copy link to clipboard

Copied

Hi,

I am trying to integrate our app with Adobe Sign API and I noticed some weird behaviour when getting information about agreements.

When I call URL, with setting x-api-user header to Andy

https://api.na2.echosign.com:443/api/rest/v5/agreements/3AAABLblqZhC2Z-XZwtMvTIaa047IkmWALZ6O1rcSXwh...​​

I get Agreement with different agreementId then I used in URL (3AAABLblqZhAZKGFOdJqlN13TKCD4NOCLBVYUmWBC8Fu8M5sNdAcjQLZxtvojWImO5Ri9xfJtxtKT81cbfzyrAepxroQ7Jfvi)

Also it's getting more weird:

- after Access token refresh if I call the same URL first with x-api-user set to Matyas and then Andy I get an agreement with correct agreementId (same as in URL) in both cases.

- if, after Access token refresh, I call this URL with x-api-user header set to Andy and then Matyas I get an agreement with wrong agreementId in both cases

It is always the same agreement and the only difference in both responses is agreementId and latestVersionId. Since I need to download information about agreements for multiple users, I am getting duplicate records in our database with different Ids.

This is very frustrating... Is it a bug? Or am I missing something?

Thanks for your reply.

Views

83

Likes

Translate

Translate

Report

Report
Community Guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more

Have something to add?

Join the conversation