Not able to send document out for e-signature for document created with the Acrobat Sign API
I am using the Acrobat Sign API to send an agreement out for e signature as outlined in the docs here https://opensource.adobe.com/acrobat-sign/developer_guide/apiusage.html#sendforsigning but my integration uses https://secure.adobesign.com not the new https://secure.echosign.com url yet.
I successfully went through the oath flow and successfully created the document in Adobe. It shows up on my Adobe Acrobat home screen under recent documents.
However, when I choose the document and click ‘Edit’ in order to add signatures to request it redirects me back to the Documents home screen. I'm not able to add recipents and signature requests to the document.
Previously, I have seen my new document under the ‘Legacy Drafts’ tab on the left and when I clicked 'Edit' I could add recipents and signatures. But in this particular test adobe account ‘Legacy Drafts’ is not in the left hand menu.
Is this a licensing problem with my Adobe account (Acorbat for teams standard)? If it is, why was I able to generate a token with my requested scopes successfully and create a document successfully? Or is it an issue that I’m still using the https://secure.adobesign.com endpoint? If I use https://secure.echosign.com would that fix the issue?
