Highlighted

Sending agreement with Adobe Sign API - error

Community Beginner ,
Mar 04, 2019

Copy link to clipboard

Copied

Hi!

I'm trying to create agreement with the use of Adobe Sign API in c#. I'm using integration key for authentication and these are access points returned to me by GET /baseUris endpoint:

{

    "apiAccessPoint": "https://api.na2.echosign.com/",

    "webAccessPoint": "https://secure.na2.echosign.com/"

}

I'm getting the same error whether I'm trying to run it in Postman client or in the application, or in "try it" page. I'm supplying "Authorization" parameter:

Bearer <myIntegrationKey>

And request body (application/json content type):

{"fileInfos":[{"transientDocumentId":"3AAABLblqZhBrIQv-DQkoZ5I9yJlf-PFB1JPEXKOcYT6VpC6yzc8rj89y5yc0fVFkitvmFers08VIWo1m8Qi6PLGOfUVUGPooSjX7s2t60hhPUA4rgVo3Wmlgu_8Z3LB5fapRWSrUgrbakL1Q-1DotAtYr2Dw-OHzxzQOicyGzRpgXhk4t92zEPA6i2FVa4b_QrSeC42nI9iy71E4yosjLTgi9XJKYzO2QLRfPNUdLkfTYfNez4QFzklwC2hY7DOVRDeHT-IiKgHQF8WGKpbZDxv7MC3pFab7hVbXYIVnD_dy02P3af6LZAhRA4hVJcpf6Z1Bh9k_q38*"}],"name":"ContractForSigning","participantSetsInfo":[{"memberInfos":[{"email":"someaddress@somedomain.com"}],"order":1,"role":"SIGNER"}],"signatureType":"ESIGN","state":"IN_PROCESS"}

This what is being returned to me in "try it" page REST API — Document e-signature Software — Adobe Sign :

Request URL

https://api.na2.echosign.com:443/api/rest/v6/agreements

Response Body

{ "code": "INVALID_API_ACCESS_POINT", "message": "Request must be made to correct API access point (e.g. use GET /baseUris)." }

I'm trying to use https://api.na2.echosign.com/api/rest/v6/agreements​ url in Postman or Imsomnia, but getting the same error.

Does it mean that this functionality is not available when using integration key instead of access token?

Thank you!

The issue was resolved by adding more permissions to Integrations key (I just added all options).

Topics

Questions Need Help

Views

1.5K

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

Sending agreement with Adobe Sign API - error

Community Beginner ,
Mar 04, 2019

Copy link to clipboard

Copied

Hi!

I'm trying to create agreement with the use of Adobe Sign API in c#. I'm using integration key for authentication and these are access points returned to me by GET /baseUris endpoint:

{

    "apiAccessPoint": "https://api.na2.echosign.com/",

    "webAccessPoint": "https://secure.na2.echosign.com/"

}

I'm getting the same error whether I'm trying to run it in Postman client or in the application, or in "try it" page. I'm supplying "Authorization" parameter:

Bearer <myIntegrationKey>

And request body (application/json content type):

{"fileInfos":[{"transientDocumentId":"3AAABLblqZhBrIQv-DQkoZ5I9yJlf-PFB1JPEXKOcYT6VpC6yzc8rj89y5yc0fVFkitvmFers08VIWo1m8Qi6PLGOfUVUGPooSjX7s2t60hhPUA4rgVo3Wmlgu_8Z3LB5fapRWSrUgrbakL1Q-1DotAtYr2Dw-OHzxzQOicyGzRpgXhk4t92zEPA6i2FVa4b_QrSeC42nI9iy71E4yosjLTgi9XJKYzO2QLRfPNUdLkfTYfNez4QFzklwC2hY7DOVRDeHT-IiKgHQF8WGKpbZDxv7MC3pFab7hVbXYIVnD_dy02P3af6LZAhRA4hVJcpf6Z1Bh9k_q38*"}],"name":"ContractForSigning","participantSetsInfo":[{"memberInfos":[{"email":"someaddress@somedomain.com"}],"order":1,"role":"SIGNER"}],"signatureType":"ESIGN","state":"IN_PROCESS"}

This what is being returned to me in "try it" page REST API — Document e-signature Software — Adobe Sign :

Request URL

https://api.na2.echosign.com:443/api/rest/v6/agreements

Response Body

{ "code": "INVALID_API_ACCESS_POINT", "message": "Request must be made to correct API access point (e.g. use GET /baseUris)." }

I'm trying to use https://api.na2.echosign.com/api/rest/v6/agreements​ url in Postman or Imsomnia, but getting the same error.

Does it mean that this functionality is not available when using integration key instead of access token?

Thank you!

The issue was resolved by adding more permissions to Integrations key (I just added all options).

Topics

Questions Need Help

Views

1.5K

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
Mar 04, 2019 0
Community Beginner ,
Mar 04, 2019

Copy link to clipboard

Copied

The issue was resolved by adding more permissions to Integrations key (I just added all options).

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
Reply
Loading...
Mar 04, 2019 1