Acrobat Sign Developer

Hi,our solution manages more than one API Application for the same account and it came up that the OAuth authorization is required only for the first application, if the scopes of the second one are the same or a subset of it. For example:APP1 -> scope: agreement_write+agreement_read+agreement_send+library_read+library_write+webhook_write+webhook_read+webhook_retention APP2 -> scope: agreement_write+agreement_read+agreement_send+library_read+library_write If we start OAuth request process for APP1 before APP2, APP2 will not ask for permissions. Is there any way to force the user to confirm the permissions for every application that requires an authorization token? 

Hi everyone,  This is my first post and I'm looking forward to establishing an Adobe Sign connect with a little help from the community. My goal is to use the Adobe server to server API to connect my Gumloop profile to my Adobe Sign and send out automated signature letters. Does anyone have experience setting this up or setting up something similar that wouldn't mind offering some guidance? I'm using Postman right now to establish the initial connection. 

Hey guys, We’re integrating Adobe Sign REST APIs and need OAuth v2 API access for our account to use REST v6 endpoints. Currently, we receive the error: use_oauth_v2_apis: /public/oauth apis are not allowed to access for this application. Please use /public/oauth/v2 apis. What do I need to do to get passed this? 

L'application Adobe Sign version mobile comporte un bogue qui ferme l'application avant d'avoir terminé de compléter le formulaire lorsqu'il y a plusieurs champs à compléter. Est-ce que ce problème sera réglé sous peu? avec une nouvelle mise à jour?

Hello,I am currently working on a project using the Adobe Acrobat Sign API, where I aim to generate contracts based on input from Google Forms. In order to proceed, I need to create a server-to-server (S2S) access token.However, when I attempt to create a new Acrobat Sign project via the following URL, the "Create" button is disabled and the following message appears:License requiredYour organization does not have a license to access this API, please contact your admin. If you think this is an error, please contact customer support.URL: https://developer.adobe.com/console/3511502/servicesandapisCould you please let me know how I can enable this or what steps are required to obtain the necessary license?

We were unable to create your agreement because we had a problem processing your document This may only be a temporary problem. However, if you have tried more than once to create this agreement with the same document, please visit our online support system.

Hello,I'm encountering an issue when creating form fields using the PUT /agreements/{agreementId}/formFields endpoint in REST API v6. This occurs specifically when the agreement is created in the Authoring state and I immediately try to apply form fields.Error response:{ "code" : "DOCUMENT_NOT_AVAILABLE", "message" : "The document is not yet available or will have no pages to view"}To work around this, I currently implement a retry mechanism that attempts the PUT request up to 10 times with a 2-second delay between tries. If it fails after 10 attempts, the process is aborted.What I've tried:1. Creating the agreement in Draft stateThis doesn't work for my use case, as I can't retrieve the participantSetId needed for assigning fields—these IDs appear to be available only after switching to Authoring state. I'm also unsure if there's a way to assign fields without having those IDs.I have also found this: https://helpx.adobe.com/sign/kb/formfields-option-is-not-available-in-v6-

We are also facing the same issue since 5:30am IST. Below is the error message. Is there some issue which the team at Adobe is aware of?Expecting 'REJECTED,RECALLED' but was 'EMAIL_BOUNCED'

Hello,I have issues integrating the adobe sign api into my companies application. I am new to acrobat and adobe sign so I do not understand the core infrastucture of the service and how adobe sign instances are separated. My main question at the moment is this:Where do I have to create an API Application?Implementing the adobe sign api was requested by one of our customers which has his own adobe sign instance (e.g. https://customer-dev.eu1.adobesign.com) but we are working on a solution that works for all customers including new ones in the future. Do my customers have to create their own api application and provide their client id and secret or does my company need an adobe account (e.g. on https://api.eu1.adobesign.com) and create the api application there once and than use it for all of our customers? Are these adobe sign instances strictly separate or can one instance use an api application of another instance?Thanks

Buen dia, al subir un archivo csv me sale el siguiente error [Recipient_1:Email]: No hay ningún encabezado de correo electrónico obligatorio. que debo hacer para solucionar este problema, Saludos

Here’s a fun experiment to show Adobe exactly how badly they’ve messed up Adobe Sign. Download the inventor declaration from the USPTO's website.  Do this by searching for "USPTO AIA 001 form," and you can get a link to the form. Open the downloaded form. Insert the name of a person as the inventor. Any name will do! Now save it as “Document 1” or whatever. Open the downloaded form again. Insert a different name of a person as the inventor. Now save it with a different filename, say “Document 2." So now you have two saved versions, each with a different inventor name inserted, right? The documents started from the same place, but as saved, they are DIFFERENT. They have DIFFERENT INVENTOR NAMES IN THEM, right? Now, go to Adobe Sign. Make a “binder” that includes both of the documents you saved. Begin to insert information to allow the inventors to sign. What’s that, you say? The names on the two documents in the binder are now exactly the same? What????? Th

Hello,I was trying to call the AbodeV6 Rest APIs using: https://secure.na4.adobesign.com/public/docs/restapi/v6#/accounts.But I am getting the error: "access_denied: Scopes not enabled for this application", while Authorizing, despite having configured scopes for my application. I performed the following steps:1. Clicked on Authorize 2. Selected all the scopes > Authorize 3. Got redirected to a new tab, which displayed an error message: "access_denied: Scopes not enabled for this application" My API Application Details:  It would be really helpful if someone could help me with this or pinpoint what I am doing wrong.Thank you!

When we create the agreement on API REST to create a user to the agreement.We use this json:{ "fileInfos": [ { "transientDocumentId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxx" } ], "name": "Legisway AdobeSign process", "participantSetsInfo": [ { "memberInfos": [ { "email": "xxx@xxx" } ],"order": 1, "role": "SIGNER", "name": "Surname Name" } ], "signatureType": "ESIGN", "state": "DRAFT", "documentVisibilityEnabled": false, "hasSignerIdentityReport": false, "isDocumentRetentionApplied": false, "status": "DRAFT" }When we are on Adobesign Interface the user is display in a group and not as simple user,How can we modify that?

Hi. I'd like to integrate adobe acrobat sign with a software that is not listed in the  list of integrations of apps of Human Resources. I´d like to do the integration with the software Tellent Recruitee. Thanks 

It has respnonse as expected but fails to register in Acrobat Sign 

Cannot find delete buttons on webhooks page on Acrobat Sign - all are inactive

We have a user with 7 webforms that they regularly need to download the CSV field data for. Unfortunately, there is a bug in Adobe Sign where if the webform has a large number of agreements it fails to download the data. So we are using an API to do this via PowerShell. I would like to automate this to export the data to a SharePoint List for each webform.The Power Automate Adobe Sign connector has various actions, including "Get a list of all webforms", which succefully returns an array of webforms for a user. However, I do not see an action to get the CSV data for the agreements signed via a webform.The API has the following endpoint which we use in our PowerShell script: https://secure.na1.adobesign.com/api/rest/v6/widgets/$WebFormID/formData Is there an equivalent action I am missing on the Power Automate connector?  If not, is the best way to loop through the webforms using the HTTP premium action?

Our credentials seem to have stopped working both for ourselves and our customers who use e-Sign via our application.  We use these credentials (secret redacted): APISelect Adobe SignClient IDCBJCHBCAABAAHVVv-hGGA60Wz2BbP9anOxNMg-5bSx0eClient SecretXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXRedirect URLhttps://localhost The message we get back in our code when we call you API doesn't include an error message, so we have no idea why this has stopped working. Please help.

Hi all, I have created an application in which I have configured the redirect uri. We have a development environment which is https://sandboxci.almeraim.com, and the production environment, so modify the redirect uri in the application, always works only by sandboxci, I do not know if it is a cache issue or something similar, in the images you can see the error message and the configuration of my application, thank you very much for the help you can give me. 

Hi, We are using the V6 API to create draft agreements via a transient document upload. These drafts now appear in the user's dashboard as "Legacy Drafts" and there is a message suggesting they won't be available after May 29, 2025. What will happen after this date? Will this process no long work to create drafts that can be edited or viewed by the user? Is there a new way that we should be creating agreeements?   Thanks for your help, - Chris  

Hi,the endpoint to retrieve the current status of an agreement returns a FetchedAgreementInfo object, which should have a property called fileInfos that is not returned.  This property seems to be the only way to enstablish a link between the TransientDocumentId added to the agreement request and the AgreementDocumentId created by Adobe Sign service. Is there another way to obtain it or is there a undocumented parameter to pass to the endpoint? Thank you

Hello *, unfortunately I currently can not request signatures. I get following API error - can anyone help?Thanks in advance  Mario 

Dear Adobe sign provided new interface for your very good application. However, the old interface was also available for user sole decision.Recently I have realised that this option "old interface" is not longer available.Based on that i was forced to use the new interface and i found something that, for my point of view, is a downgrade on the app. For meetings with more than 10 attendees, i used to use excel to collect emails and names. Once those were there (in excel) i used to open the old interface of Adobe sign, and making a kind of copy and paste (in once) of more that 10 representative emails directly to the adobe sign. Sucessfully used to be the process for more the 3 years.Now with the new interface, i need to copy and past every single email to the correspond field. More than that, i need to client "add" to open a new field for new copy and past of representative email. Something that used to spent 2 seconds, now became, more than 5 minutos. Terrible. in a

I built templates in my adobe sign (computer) I want my staff to be able to get signature on a tablet on those templates. But the ios app does not sync the templates .... is it possible to do so ?  I do not want to use the template by sharing them on dropbox because I realized that calculated field do not transfer from adobe pro to adobe sign. (need to reenter the formula)  Thanks

I use Adove Sign for a major international company. 1. There is no interoperability between Adobe Acrobat and and Adobe sign - randomaly ignores fields, override already-filled data, ignores actions between fields...2. Decides to add fields where there aren't any, even when I say "Do not auto-detect"3. Can't rearrange pages after the initial stage.4. login and signing windows load and close with media (There is no need of a nice pictorial background for a prompt that opens and closes in the background for 1.2 seconds!) It use to take 10 seconds to sign a document. Now it takes me 5 minutes. This is unbareable. Devs, hear me out. I hope Adobe guys are working on this.