Questions

DescriptionWe are integrating Adobe Acrobat Sign with our application using OAuth 2.0 authorization code flow.Our application sends the state parameter as a URL-encoded, JSON-serialized string containing the context required to complete account creation. We understand that Adobe's documentation defines state as a string; we are not assuming that JSON is mandatory or that Adobe requires JSON-formatted values.However, we have observed that the value returned to our callback appears to differ from the value sent in the authorization request.Outgoing state (after URL decoding):{"service":"Adobe","serviceId":"Adobe","securityType":"OAUTH_JWT",...}Returned state (after URL decoding):{"service":"Adobe",...}The outgoing value is valid JSON. The returned value contains HTML entities (") instead of quotation marks, so it is no longer valid JSON as received by our application.We verified that the outgoing value is correctly URL-encoded and that Adobe's

I have an Adobe Acrobat Sign developer account and registered an OAuth application for a test manuscript-submission workflow. The OAuth authorization flow completes successfully and returns a token with the user_read:self scope.In the app’s OAuth scope settings, agreement_write:self and agreement_read:self are unavailable or disabled. The page indicates that support must be contacted to change the available scopes. Adobe’s virtual assistant also says it can’t associate an active Acrobat Sign plan with my account.Is this expected for a developer account? Can these agreement scopes be enabled for a developer or test application without purchasing a paid Acrobat Sign subscription? If a paid plan is required, which lowest-cost plan supports these scopes and API testing?I’m looking for the right technical guidance or support channel. I have not included credentials, application IDs, or secrets.

Case description:I want to use the "Send in Bulk" feature in Adobe Sign to import a CSV file with data, automatically populate a document, and send it to 4 signing parties.For this purpose, I created a document template containing text fields named identically to the column headers in the CSV (e.g., "StudentFullName"), and signature fields for 4 signers are defined on the last page (in no particular order). Each line in CSV contains 4 recipients/signers and "Merge data" to populate the document.My issue:The CSV data import process completes successfully, but only the first signer is imported—the remaining signers are not. All other data is correctly imported and populated into the document.I suspect the issue lies in the CSV file, specifically in the header indexing for the individual signers, as the original CSV template from Adobe does not include indexing. As a result, it is unclear how the indexing in the CSV should be formatted or defined so that the process correctly identifies t

The answer is yes, and I thought other Acrobat form developers might be interested in an alternative approach I eventually developed.Years ago, Acrobat provided ODBC database connectivity that made it possible to connect a PDF form to an external relational database. After that capability was discontinued, I spent considerable time looking for another way to provide database-like record management from within a PDF form.I eventually developed a different approach using Acrobat JavaScript, a JavaScript object, JSON, and hidden PDF form fields.Rather than connecting the PDF to an external relational database, the records themselves can be stored and managed within the PDF.The JavaScript object provides the working structure for managing the records. JSON provides a compact means of serializing the structured data, while one or more hidden PDF form fields provide persistent internal storage. Acrobat JavaScript ties everything together by controlling how records are created, retrieved, sea

Is there anyone from Adobe Acrobat Sign tech support monitoring these community forums? I would like to test out the ‘Send On Behalf of Another User’ feature using my Developer Account as part of a prototype integration I’m working on for a customer. It’s not clear if this feature is enabled for Developer Accounts as I keep getting this error:{"code":"INVALID_ON_BEHALF_OF_USER_HEADER","message":"Value provided in x-on-behalf-Of-user header is in invalid format"}I can’t seem to contact anyone at Adobe any other way except via this community forum but it looks like no-one is actually monitoring? Is there another way I can get an answer to my question?Thanks

I’m using the Developer Account to test out an integration using the Adobe Acrobat Sign API. I have been able to successfully send agreements via the API.I’m now testing out the use of the:x-on-behalf-of-userheader to send an agreement on behalf of another user. I have added a 2nd user to my Developer Account and have logged in as them and shared access to the admin user of the Developer Account. I followed the steps under the Basic Sharing option here:https://helpx.adobe.com/sign/web/users/sharing-user-content/overview.htmlWhen I attempt to upload the Transient document using the x-on-behalf-of-user header I’m getting this error:{"code":"INVALID_ON_BEHALF_OF_USER_HEADER","message":"Value provided in x-on-behalf-Of-user header is in invalid format"}I found another article that says that “For Send on behalf function, enable Advanced Account Sharing for the account so that users can give sending permissions to other users while sharing their account” when using the REST API. I’m not seei

Hi, I'm building a monday.com marketplace integration that connects to Acrobat Sign via OAuth (Authorization Code flow). The app is designed so that each of monday.com customers (separate organizations) will connect their own individual Acrobat Sign account to our app.I registered my OAuth application under our Adobe Developer Console account, then tried testing the flow using a separate Acrobat Sign Business trial account under a different email, to simulate a real customer connecting their own account.The OAuth flow returns:error: access_deniederror_description: User cannot authorize access because it is UNCERTIFIEDBased on Adobe's Developer Terms of Use (section 20.4(C)): "You must enter into a separate written agreement with us if you wish to sell, distribute, or offer Developer Software that is designed to interoperate with Acrobat Sign API."My questions:Is this "UNCERTIFIED" error specifically tied to the certification/agreement mentioned in section 20.4(C)? What's the exact proc

Hello,Reading the API documentation seems that agreements cannot be created with webhooks in a single POST request.I’m implementing a partner solution and for each customer that wants to sign documents I need to:check if the customer account already has a webhook created for my application (GET /webhooks).  (because I don’t want to fill the customer account with hundreds of webhooks) if not, create the webhook at account level (POST /webhooks) And then, create the agreement (POST /agreement)Doing 2-3 http requests looks inefficient just to simply create an agreement with notifications.I found this thread that stays what I said: However, it’s 3 years old and things may have changed. Is it still the same? Or do you plan to have it like Docusign does?Thanks

El Documento a firmar, tienen UNA SOLA VENTANA O CASILLERO PARA FIRMAR. Y en ese casillero viene “incrustado” un logo; para colmo de una organización guerrillera de Argentina de los años ‘70. El ERP… ¿Que esta sucediendo? 

Hello,We are currently experiencing an issue when trying to create a new webhook via the API (POST /webhooks). The API consistently returns an HTTP 400 error with the following payload:{"code":"INVALID_WEBHOOK_URL", "message":"Validation for webhook url failed. Please make sure that the webhook url responds with a valid HTTP response code and a valid client id."}Here is the context of our troubleshooting so far: Our webhook endpoint is publicly accessible. Our application is configured to correctly intercept the X-AdobeSign-ClientId header from your GET validation request and echo it back in the response headers with a 200 OK status. However, our server logs show that Adobe Sign's validation GET request never reaches our application. > We successfully tested our code using a public testing URL (webhook.site), and the webhook was created perfectly, proving our code and API payload are correct. Upon analyzing our test environment's infrastructure, we noticed that our SSL configura

In the authoring screen, Field Templates option is suddenly missing today.  The templates allow us to place multiple form fields designated for each signer.  Now we must place form fields one signer at a time without the benefit of a preset template.Field Templates option available yesterday.Field Templates option missing today

 Designing a webhook + polling architecture for an existing OAuth-based integration. The polling layer is intended to serve customers whose application servers cannot expose a public webhook URL (private IP, VPN-only access). Five questions where the docs aren't conclusive: 1. MOPI scope on GET /agreements (the list endpoint) The Minimum Object Polling Interval policy applies to "all GET API endpoints." For GET /agreements/{agreementId} the polled object is clear. For the list endpoint GET /agreements (no path ID, returns a paginated list), it's not.Two plausible interpretations:The list itself is a single polled object. Calling GET /agreements more than once per 10-minute window (non-Enterprise) or 3 times per minute (Enterprise) returns 429 / 304. Each agreement in the response is the polled object. Successive calls to GET /agreements are unrestricted as long as the same agreement isn't returned more frequently than allowed.Which is correct? This determines whether GET /agreements is

Borré un archivo escaneado en Adobe Scan sin intención y quiero recuperarlo  

Dear Adobe Partner Team,As a software partner specialising in solutions built on Microsoft Dynamics 365 Business Central. We have developed an integration between Business Central and Adobe Acrobat Sign  that allows our customers to send documents (quotes, agreements, terms of delivery) for signature directly from Business Central, using the Acrobat Sign REST API via Azure Logic Apps.We would like to offer this integration as a product to our Business Central customers, following an "Integration Only" model: each customer brings their own Acrobat Sign licence, and we deliver and maintain the connector.We would be grateful for your guidance on the following:1. How does the ISV / integration partnership for Acrobat Sign work at the moment? We have noticed that the registration portal for the Adobe Exchange Program for Document Cloud appears to be closed to new registrations – what is the correct route to apply today?2. What does the certification / approval process for our integration in

A customer is migrating from Tailored to Adobe Sign FedRamp.  Their admin needs to claim the domain, but cannot find the email to do so and we need to get this moving as soon as possible.  How can we have that email re-sent to him today?  Thanks!

I created a new developer account, but I don't have access to the Adobe Acrobat Sign API. When I try to create a project to request API access, it doesn't appear as an option

Hi folks, I am using the Java SDK for years now, it was working and I didn’t change anything on my site. Now (since about 2 weeks or more) I have the following problem:After creating an Agreement and setting it to state AUTHORING I want to update the form fields. The relevant part in my code including debugging additions is this:try { agreementsApi.updateFormFields(authorization, etag, id, formFieldPutInfo, xApiUser, xOnBehalfOfUser);} catch (Exception e) { agreementInfoHTTP = agreementsApi.getAgreementInfoWithHttpInfo(authorization, id, xApiUser, xOnBehalfOfUser, ifNoneMatch); etag = agreementInfoHTTP.getHeaders().get("etag").get(0); System.out.println("etag: " + etag); throw(e);}However this now leads to an ‘io.swagger.client.model.ApiException: Precondition Failed’ and returns ‘{"code":"RESOURCE_MODIFIED","message":"Resource is already modified with newer version"}’. When using the GET /agreements/{agreementId} here with authorization and agreement id I get the exact same ETag in th

 regarding the validity of signing URLs generated using the getSigningUrls method in Adobe Sign for Salesforce. And also https://helpx.adobe.com/in/sign/using/adobesign-document-link-expiration.html this are same or not. Why i ask you beacuse, getSigningUrls get me in response body.

I want to edit the email adresses in “cc” of an existing web form because of changes in the reponsibilitys. How can i do this?I find no way to edit. Only solution right now for me is to create a complete new web form. This would be very much effort. 

How can i  enable Anchor Text (ANCHOR_TEXT) for my Acrobat Sign developer account ?

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