• Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
    Dedicated community for Japanese speakers
  • 한국 커뮤니티
    Dedicated community for Korean speakers
Exit
0

externalId use

New Here ,
Jan 31, 2018 Jan 31, 2018

Copy link to clipboard

Copied

I am successfully able to send an externalId as both an agreement level and documentCreationInfo level value. However, I cannot successfully query by either value using (for example) either:

https://api.na2.echosign.com/api/rest/v5/agreements?externalId="CPQ-Agreement-GUID-DocumentLevel"

nor

https://api.na2.echosign.com/api/rest/v5/agreements?externalId=CPQ-Agreement-GUID-DocumentLevel

Also, it appears that both externalId and callbackUrl are not visible via the API. Is there a way to force these values to be returned?

Views

764

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
community guidelines
Community Beginner ,
Sep 08, 2021 Sep 08, 2021

Copy link to clipboard

Copied

Hi,

Could you solve this issue?

I have the same problem.... 

I'm passing the externalid parameter in POST /agreements method but I have no luck with the query in GET method.

When I try to filter by the externalid no agreement is found 

Votes

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
community guidelines
Adobe Employee ,
Sep 09, 2021 Sep 09, 2021

Copy link to clipboard

Copied

LATEST

Works for me using v6 ethod

get /agreements

 

Votes

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
community guidelines