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

Problem with sending agreement by API

New Here ,
Jun 23, 2023 Jun 23, 2023

Copy link to clipboard

Copied

Hi,

 

I'm integrating Adobe Sign to a software product and thus do a bit of testing with the API. This means I have sent the same document several times.

Now I get an error saying there was a problem with the document and that I should contact support if I tried to create the same agreement with the same document. Well, I did, as I said I am testing.

It seems now that I have locked something for security reasons or whatever. When I send a get request to the API to list my agreements, the recent ones are in state cancelled.

Is there any chance to reset this lock, so I can go on with my work? Or might there be another problem involved?

 

Cheers

Benjamin

TOPICS
Manage security and compliance , Send documents

Views

220

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

correct answers 1 Correct answer

New Here , Jun 26, 2023 Jun 26, 2023

My problem was that I sent the transient document in base64 encoding instead of binary. The API didn't complain, so I thought all was well, I also thought I had read somewhere to send it base64 encoded but cannot find it anymore.

Later when it tried to make use of the document, the API found out that this is no pdf binary, thus the error. Wish the error message had been more specific and not been talking about sending the same document several times, so I thought I had been locked.

Anyway, lesson

...

Votes

Translate

Translate
New Here ,
Jun 26, 2023 Jun 26, 2023

Copy link to clipboard

Copied

LATEST

My problem was that I sent the transient document in base64 encoding instead of binary. The API didn't complain, so I thought all was well, I also thought I had read somewhere to send it base64 encoded but cannot find it anymore.

Later when it tried to make use of the document, the API found out that this is no pdf binary, thus the error. Wish the error message had been more specific and not been talking about sending the same document several times, so I thought I had been locked.

Anyway, lesson is: Send document in binary format.

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