Questions

I’m sending documents for signing through REST API and in certain cases I would need QES approved signature in EU area. I have set recipient authentication method to be selected case by case but that is not enough to achieve QES signature. How can I configure agreement so that when signers open the link from email, it automatically requests QES applicable signature?Also in certain cases AES signature is needed, how to achieve that? Is recipient authentication method set as “Government ID” enough to achieve AES approved signature?

Is anyone else having this issue? We have 10 customers who we integrate with and send documents for signature through their Adobe Sign accounts. Half of them no longer recognize the signature tag and place the signature at the end of the document, while others are still working fine. Trying to understand what in the new release may be causing this or if we need to make a change going forward.

We have a requirement to replicate workflows from an old Adobe Sign instance to a new Adobe Sign instance.After reviewing the Adobe Sign REST API documentation, we do not see a POST or equivalent endpoint that would allow Workflows to be programmatically created, cloned, or recreated in another instance. To confirm supportability, could you please advise on the following:1.    Is there any supported method (API-based or otherwise) to export, clone, or recreate Workflows from one Adobe Sign instance to another?2.    If this is not supported via REST API, are there alternative supported approaches (e.g., admin tooling or Adobe Professional Services capabilities) for Workflow migration?3.    Are there any known limitations or constraints specific to migrating or rebuilding Workflows during tenant separation scenarios?4.  Can you provide any idea or any implementations in the past?

I am setting up an API application for Adobe Acrobat Sign and trying to configure the redirect URL within the OAuth settings of the registered app. However, the URL is always rejected as invalid.The page is hosted on an SAP system and is only accessible within my company network, meaning it cannot be reached by Adobe Acrobat Sign. Could this be problematic?Or does the URL need to follow specific patterns that I might not be aware of?The url works just fine, if im opening it in the browser directly.The URL in question is:https://XXXXXX.XXXXXX.INTERN:8443/sap/bc/ui5_ui5/inn/e4_XXX/index.html 

I’m using the Adobe Sign package(Developer Account) in Salesforce to automate the process of sending agreements through Flow Apex actions. However, after the customer signs the agreement, the Agreement Status in Salesforce is not being updated to ‘Signed’ or ‘Completed’, but in the Manage agreement that agreement is in the Completed section 

 Hello Adobe Acrobat Sign Community, I’m integrating Adobe Acrobat Sign with a custom workflow and running into multiple roadblocks:1. Agreements Auto-Sending•Goal: I want to create an agreement in an “AUTHORING” or “DRAFT” state, add my custom fields (including signature fields), and only then explicitly send it out.•Issue: As soon as I use the PUT /agreements/{agreementId}/formFields endpoint to add custom fields, the agreement automatically transitions to “OUT_FOR_SIGNATURE” and is sent to the signer, even though I never manually changed its state to “IN_PROCESS.” Question:How can I keep an agreement in a non-sent state until I explicitly trigger sending? Is there a way to prevent Acrobat Sign from auto-sending upon form-field updates? 2. Custom Signature Fields Overridden•Goal: I want to define my own signature or initials fields at specific locations in the PDF (via the PUT /agreements/{agreementId}/formFields call).•Issue: Acrobat Sign often replaces/ignores m

Is it possible on a Developer account to have more than 2 WebHooks? We have many development and testing environments and would like to have a WebHook pointing to each for consistency. We will have a fully licensed account for production, but do not want to have a licensed account for these development and testing setups as we do not want to burn through our transaction allotment.

Hi, Unable to add user using email. Pls. provide steps how to add and what is missing. Should you need a call arrangement, pls. reply in the email and I will respond.  Thanks

We have created a Webform by uploading a PDF and added a Signature block to the webform. On submitting the website , it asks for Verify of EMail Address send on an email id provided along with the SIgnature. Once email address is verified , a email is send with a body content having a URL which contains the form details submiited by user along with signature. We need to send email with the PDF attachment with the submitted form details  & signature.Is it poosible OOTB or can it be achieved via API integration.

Hello, I wanted to know what level of access one needs on Acrobat side in order to use that account for integrating with Salesforce for E Signature. I am guessing System Administrator access is required but needs confirmation. Could anyone please answer this question?

I am trying to create a modal using an iframe element to show the editing a document page, I figured out I need to have the user_login scope for the Integration Key that I am using. But I dont want to go that route or else I will have to change that for all my accounts and in all environments.  Is there a simpler way to show the edit page onto an iframe? Or is modifying the integration key scopes the only way? Thanks

Hi,I want to know how many webhook requests were sent, how many were successfully processed, and how many failed—for example, over the course of a week. Is there any way to find this out from the Adobe side, using response codes such as 200 - SUCCESS or 500 - FAILURE?Thanks,Sreejesh

We have few documents which were partially signed (outside of adobesign). These documents need to be send for futher esignatures using API.Is this usecase supported by Adobe? If yes, how do we proceed?Note that same documents when uploaded on Adobesign UI, are able to be sent for esignature, but when sent by API are declined

Hello,I'm using following endpoint for delegating:/agreements/{agreementId}/members/participantSets/{participantSetId}/delegatedParticipantSets My account has agreement_write scope enabled with group modified.My content type for tests is: { "memberInfos": [ { "email": "someEmail@address.com", "securityOption": {} } ] }  I'm getting follow error:{ "code": "PERMISSION_DENIED", "message": "The API caller does not have the permission to execute this operation" }Response Code: 403 Is there a bug in the Adobe Sign API? What persmission do I need?

Hi When I try to create Reusable Templates, I dont have any option to select the type of the template.  When I try to use the template, it inserts the document which I used for creating the template vs Form Fields.  I have Acrobat Sign Prepaid Plan.  I have seen any option to enable this feature.   Based on the posts it is a enabled by default.    

Hi, I canceled a document sent to me thinking that it was a mistake, unfortunately, the people who sent it  to me have a system that generates these Orders automatically and cannot resend it. Can someone please help me restore the document so I can sign it?Thanks in advance

Dear, I have a dotnet application to upload document and e-sign by Adobe e-signing API v6. I am trying to add a placeholder for the signer in the document. here is the screenshot of the document below. It is a PDF. I want to replace signer1 signature and initials with the fields.  My upload is successful by the API call "/transientDocuments". And then I am calling API "/agreements" with the transientDocumentId. In my request I am sending the state as "AUTHORING" and not mentioning any email address. because I do not want to sent it for the signature. I want to see the document with the placeholder fields in Adobe. here is my JSON input for agreement API call. {"name": "Test update Object","type": "AGREEMENT","signatureType": "ESIGN","state": "AUTHORING","message": "","participantSetsInfo": [{"memberInfos": [{"securityOption": {"authenticationMethod": "NONE"},"placeholderName": "SIGNER1"}],"role": "SIGNER","order": 1,"participantSetId": "signer1"}],"fileInf

The Adobe sign APIs require users to authenticate via OAuth flows To make the user experience in our app more fluid, is it possible to use a service/techinal account or maybe even service to service oauth credentials when authenticating with Sign APIs on behalf of our users. The authorization request will usually lead to a user logging in with their own crednetials. I have been tinkering with the above but have been unable to get them to work with the Sign APIs. I see there is a legacy "Integration API key" option available, but I think OAuth is a requirement for new applications. Without some sort of service/technical account, users would each have to authenticate with adobe sign when sending a document for signing for the first time. It would be preferrable if an admin was able to configure Adobe Sign once for everyone in the account.

UrgentWe are using the Adobe Sign API to retrieve and store signatures within a Nintex workflow. Adobe provides two relevant actions: Get Signature and Store Signature. In our implementation, we have integrated Azure Functions within our connector service to interact with various Adobe Sign API endpoints, including agreement retrieval and more.One of our customers is experiencing intermittent issues while executing the Get Signature method. This method triggers an HttpClient call from within our .NET Azure Function. While the request occasionally completes successfully, it often fails with one of the following exceptions:1. System.Net.Sockets.SocketException vbnetCopyEditThe request was canceled due to the configured HttpClient.Timeout of 100 seconds elapsing. The operation was canceled. Unable to read data from the transport connection: The I/O operation has been aborted because of either a thread exit or an application request.   2. SSL/TLS Exception vbnetCopyEdit

Hi all, We are currently working on replacing our existing text tag implementation, which we use to define signature fields in Adobe Acrobat Sign. While text tags are still functioning correctly on our end, we've seen reports from some users indicating that text tags may not function properly in the new Acrobat Sign e-signature experience that Adobe is gradually rolling out. We’d like to confirm whether this is expected behavior. If text tags are indeed being deprecated or limited in the new experience, what alternatives are recommended? We’re using a developer account, and we’ve noticed that the Anchor Text feature appears to be available only for enterprise accounts. Can this be used as a replacement for text tags in our case, or is there another recommended approach? Any guidance or official documentation would be greatly appreciated. Thank you!

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?