Questions

As a user of Adobe Sign when I'm progressing through my workflow, the text inside each label identifying what that field is responsible for, blends in with the background and I'm unable to see what tool label I'm selecting. These forms are highly sensitive for our clients personal records, so accuracy is everything and this color pallette interupts my workflow as I'm sure it does for many other workers. Thanks!

Whenever i upload a pdf document to the transientDocument endpoint, i always get a transientDocumentID and i'm also able to use it to create an agreement but whenever i try to add fields to the agreement, i get a message "The Agreement is not in Authoring Mode". When i check the status of the file, it shows that the agreement is Cancelled and then i get a mail from adobe:Have changed the pdf being uploaded to test if its an issue with the document but its not, the same thing happens for every pdf document i upload. But whenever i use the adobe sign api rest v6 page to upload the same pdf files, i don't get any errors and it works. This is my code for uploading the document:headers = { 'Authorization': f'Bearer {ACC_TOKEN}' } file = { 'File-Name': 'coo.pdf', 'File': open('coo.pdf','rb') } updoc = requests.post("https://api.eu1.adobesign.com/api/rest/v6/transientDocuments",files=file,headers=headers) Whenever i add the 'Content-Type' as 'multipart/form-data' the upload does

Hi,I have contact support for this error and they keep asking me to contact Enterprise Team through call. I can't call them and I am using a Developer Account which I believe should not be a problem.Error: The URL provided is not a valid Webhook URL.  Here's my code clearly setting the Header base on the ClientId,   [OperationContract] [WebInvoke(Method = "GET", RequestFormat = WebMessageFormat.Json, BodyStyle = WebMessageBodyStyle.Wrapped, ResponseFormat = WebMessageFormat.Json, UriTemplate = "AdobeSignNotification")] public string AdobeSignGetVerified() { /////// var currentWebOperationContext = WebOperationContext.Current; var outgoingResponseHeaders = currentWebOperationContext.OutgoingResponse.Headers; var incomingRequestOrigin = currentWebOperationContext.IncomingRequest.Headers["Origin"]; outgoingResponseHeaders.Add("Access-Control-Allow-Origin", incomingRequestOrigin); /////// var headerClientId = currentWebOperationContext.Inc

We have a group business account, and use a couple templates/workflows for our expense approvals and employee travel approvals. The purchasing expense approval works well, but the travel does not. The field that has issues is a calculated field, which totals other numbered fields and calculated fields. When the form filler completes the document, this field is visible and totals correctly. We require 4 signatures on each document, and during this signature process, this 'total' calculated field is lost. It is the only field to disappear. When I remove all the other emails from the workflow and just use my email, the document works perfectly. It's only when additional emails are included on the workflow does the problem arise. Please advise, any help would be greatly appreciated! 

Hi, I have created  a adobe sign web form and it is created with participant role as form filler. when the form filler submit this form he has to enter his name and email in a pop up. I already unchecked the check box in the Account Setting -> Signature Preferences -> Web Form Email Verification and that didnt help in hiding the pop up.Is there any way we can avoid showing that popup.Please help. Also I cant see the acceptor role when I created the web form. Giving acceptor role will make this work ?I want an user to fill the form. Upon submitting filled form, data will be processed. Thanks,Sreejesh

"I created a simple Python app to download all my signed documents and audit reports from Adobe Acrobat Sign.However, I’m unable to proceed with obtaining the API key.It seems that my Basic plan doesn't provide access to this feature.Is there any solution for how I can move forward?If you'd like to review the code, it's attached in a .TXT file.In the attached image, you can see the restriction preventing my Basic account from accessing the API."

I am not getting object name Opportunity  in the list of salesforce objects when I am creating agreement Template. I am seeing Opportunity/Quote:Competitor and Opportunity/Quote Partner in options.How to choose Opportunity/Quote (Opportunity api name) as Main source object?

Hola ! no encontramos la manera de que el Administrador pueda habilitar la fucion de MODIFICAR ACUERDO a los usuarios. Podrian ayudarnos ? Gracias !! 

The problem happened when I upload a pdf file through the ms form and process through power automate with the steps: Upload a document and get a document ID and Create an agreement from an uploaded document and send for signature,  and tried to digital sign the file on software. It reported as an unknown error and cannot be signed. But when I open this original file and sign it directly, there is no error.This proves that through the 2 steps Upload a document and get a document ID, and Create an agreement from an uploaded document and send for signature, the file has been changed somehow. How can I fix this problem? Thank a lots for any help in advance.

I am using Array variable, Compose signers action in power automate to get email addresse of 3 signers.  I use this compose output for recipient of adobe sign. But error:{"code": "INVALID_EMAIL","message": "Invalid email: ["xxx@gmail.com","yyy@gmail.com"]"}The output of compose action  as of below:["hxxx@gmail.com","yyy@gmail.com"]Anyone can help? I tried to search online but no solution found.The signer is depend on department name, dynamic.Thanks a lot for any help.

I created a power automate flow in MS365 and use adobe sign: Create an agreement from an uploaded document and send for signature.This is for multiple approvers. I want to get approvers email address from previous step by action: ComposeBut in some case, may be 1 or 2 approvers have blank value of email address. Then the flow will be failed.How to prevent of failed action in case of blank email?Because the approver list is dynamic, depend on requester.  Any help or suggestion would be appreciated.  

I am using power automate integrate with Adobe sign.  But the flow returnred the error below:We were unable to create your agreement [DEMO USE ONLY] payment test because we had a problem processing your document xxx.pdf.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.My pdf file is under 20MB.2 actions in flow:- Upload a document and get a document ID- Create an agreement from an uploaded document and send for signature How can I fid out and fix this issue? Thanks  in advance for any help.

I used adobe api and created java application and running it from one server 10.30.32.45 which private and i am added callback url for it in adobe esign application in ouath 2.0 configuration for redirect url url :https://10.30.32.45:443/icsapis/agent/oauth/callback like this but it is not working so i want to confirm will Adobe servers can access private IP addresses like 10.x.x.x directly.

Hi,I got an the following error on calling upload document API (/transientDocuments)  using .net code:We were unable to create your agreement [DEMO USE ONLY] 0707test because we had a problem converting your document 101112 - Captiva Series II Product Overview - Copy (9).pdf to PDF.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.  To ensure that you continue receiving our emails, please add adobesign@adobesign.com to your address book or safe list. but working fine using postman with the same file, and please find the .net code calling the API (Copy from postman code and used before):  var client = new HttpClient();var request = new HttpRequestMessage(HttpMethod.Post, adobeSignApiUrl + "transientDocuments");request.Headers.Add("Authorization", "Bearer " + token);request.Headers.Add("Cookie", "JSESSIONID=21D6CF196F61CD00C6869452F4EBA735.we

Hello, I keep on getting inavlid request error. Can anyone tell what could be the issues.Error: Unable to authorize access because the client configuration is invalid: invalid_requestBelow is my URL: https://secure-na3.adobesign.com/public/oauth/v2?response_type=code&client_id=clientId&redirect_uri=https://www.google.com&scope=user_login:self&state=random1234

I am integrating the adobe sign functionality in angular. When i am trying to open the authorization url in iframe , I am getting the error related to CSP

Been trying to create an agreement with form fields adding using the REST V6 API. We can't use a template as the PDF is generated in code and can have unique content and branding. This is what I have so far:Create transient document from PDFCreate an agreement as AUTHORING, pointing to transient, with a single signerGet the agreement data back, so I can get the the Assignee ID for the participantUse PUT to add form fields, setting the Assignee value as aboveSend agrement by PUT to change status to IN_PROCESS When I do this last step, I get a 401-forbidden, OPERATION_NOT_ALLOWED error. HOWEVER the agreement is sent out???!! Another question: can I put two signature blocks for separate parts?? We have a direct debit agreement on the same page which needs its own distinct signature. This is possible on a "certain other competitor platform". 

Olá, Estou enfrentando um problema ao usar a API do Adobe Sign para fazer o download de um documento. Ao executar o endpoint de download no Postman, consigo abrir o arquivo normalmente. No entanto, quando faço uma requisição via tela do meu sistema, o arquivo é baixado, mas ao tentar abri-lo, é solicitada uma senha. Aqui está a requisição dos detalhes do documento em questão: curl --location 'https://secure.na3.adobesign.com/api/rest/v6/agreements/{agreementId}' \ --header 'Autorização: Portador {accessToken}' Resposta da requisição:{ "id": "{agreementId}", "name": "[DEMO USE ONLY] Tags de teste Adobe_UsuarioTeste3_Aceite Integração Adobe - Parte 1.pdf", "groupId": "{groupId}", "tipo": "ACORDO", "participantSetsInfo": [ { "id": "{participantSetId1}", "Informações do membro": [ { "email": "{memberEmail}", "deliverableEmail": verdadeiro, "nome": "teste1", "id": "{membroId1}", "opçãodesegurança": { "authenticationMethod": "NENHUM", "identidadeCheckInfo": {} } } ], "papel": "SIGNATÁRIO", "

I have a simple question,Do we need to configure some settings, while creating Oauth app to get the Client Secret Key,Cause While creating Oauth App for Adobe sign only getting Client Id not the secret.

Olá, Estou enfrentando um problema ao usar a API do Adobe Sign para fazer o download de um documento. Ao executar o endpoint de download no Postman, consigo abrir o arquivo normalmente. No entanto, quando faço uma requisição via tela do meu sistema, o arquivo é baixado, mas ao tentar abri-lo, é solicitada uma senha. Aqui está a requisição dos detalhes do documento em questão: curl --location 'https://secure.na3.adobesign.com/api/rest/v6/agreements/{agreementId}' \ --header 'Autorização: Portador {accessToken}' Resposta da requisição:{ "id": "{agreementId}", "name": "[DEMO USE ONLY] Tags de teste Adobe_UsuarioTeste3_Aceite Integração Adobe - Parte 1.pdf", "groupId": "{groupId}", "tipo": "ACORDO", "participantSetsInfo": [ { "id": "{participantSetId1}", "Informações do membro": [ { "email": "{memberEmail}", "deliverableEmail": verdadeiro, "nome": "teste1", "id": "{membroId1}", "opçãodesegurança": { "authenticationMethod": "NENHUM", "identidadeCheckInfo": {} } } ], "papel": "SIGNATÁRIO", "

Hello, new to adobe document generation API need assiatance in using https://developer.adobe.com/document-services/docs/overview/document-generation-api/ .We have a requirement to display checkbox/radio buttons in template document and get them checked based on the values passed in the JSON file.  Unable to find any such examples, any response in this regard is highly appreciable. 

Hello,I am using Adobe Acrobat Sign for Salesforce add-on to sign documents, but I am getting an error when adding three signers.Anyone can help to fix this issue ?Thanks

I am using Adobe Acrobat Sign Rest API to sign the uploaded document. In this, I am creating a document using the below-mentioned request.API: /agreements - POSTRequest:  { "participantSetsInfo": [ { "role": "SIGNER", "order": 1, "memberInfos":[ { "email": "abc@xyz.com" } } ], "name": "API Agreement", "signatureType": "ESIGN", "fileInfos": [ { "transientDocumentId": "CBSCTBABDUAAABACAABAAYt3DTQ_oe4E_Zi4USbr1xch2lGNOGMF4LX_oG1jX5OtB7MaXRK9wpKNpIAdKSxndMM5jhefLFqb9XGKXwVY6UTfQG8KNBrgZiMLvw8uKz2nuO5z5iSH-N6FUFRdnii5Sq238kAu_MBpqc2f8EcYMJloKxlj4du4fRhwKD8mGBZRihbJ3qwp2HF5Ekiqaq-iPokxMYfDfDCR5xZie6IoG-gdKrkdGqb7ErS0QDwDMP9yGySfEjF9Xu0zQlfFMHGtYbrTrsZFh0cEE_yz4RaG18IyoLpBzC0ZtVn7gnOg8o7H33eNXib7McaIpglECHgnohfoW-btc4t7DizU0b4TSIOYKK8qXYOoEjka-fsEhgvs*" } ], "state": "IN_PROCESS" } But when fetching the agreement details using the API below, I get the response below.API: /agreements -> GET&

We are using Adobe Acrobat and are in the process of upgrading Salesforce by moving to a new Salesforce instance. As part of this upgrade, we will be installing Adobe Sign on the new instance. When we begin using the new instance, we want to migrate all agreements from the existing instance to the new instance.Our goal is to transfer all data related to Adobe Sign to the new Salesforce instance. We seek your support in this migration process.Additionally, we will be migrating data for other standard and custom objects, which will require time. Therefore, we need to use the same Adobe Sign account on both the existing and the new Salesforce instances concurrently during this transition period.  

I am attempting to add Adobe Sign API to my application in order to get a couple signatures for a report which is created using DevExpress XtraReport. I run the report, create the PDF, and want to add digital signature fields using Adobe Sign API for a staff member and their supervisor. I have tried different ways to add the signature fields but am not having any luck. One way I am trying right now is to use the /agreements/{agreementId}/formFields however it is not creating the fields. If anyone has any suggestions please let me know. Thanks!