Acrobat Sign Developer

We have a Java-based application that interfaces with Acrobat Sign.We have an Access Token (expired) and a Refresh Token (not expired). When we attempt to use the Refresh Token to get a new Access Token in Production, we get a 401 Unauthorized: [no body] error. Here's what we've tried:Taking the exact Client ID, Client Secret, Access Token, and Refresh Token from Production database tables and manually doing the POST via cUrl - this works, we get a new Access TokenRepeating #1 but with Postman - this also worksCopying the database rows down to a Dev environment and running the same code as Production - this also worksIs it possible that Acrobat Sign blocked our Prod Server?  I know for OAuth Code Flow, we have to whitelist the Redirect URI, but I thought that calls to get a new access token from endpoint: https://api.eu1.documents.adobe.com/oauth/v2/refreshcould be done from anywhere without whitelist.  Any thoughts/suggestions?

Hello, I've set up an integration between our ServiceNow instance and my Adobe Acrobat Sign account. I'm able to post an agreement from ServiceNow, with a document and a couple of participants. It's appearing in my 'In Progress' Agreements queue, with the correct recipient, and it has status 'Out for Approval'. All looks good, except that the email has not actually been sent out: I've checked that the recipient email address is correct and that the message is not going to junk or being deleted. I've sent a reminder (from within Adobe Sign itself, not via ServiceNow) and the reminder HAS been sent and received OK. If I generate the agreement directly in Adobe Sign, again the email does go out and is received. Also, ServiceNow IS receiving a webhook post from Adobe confirming that the agreement is out for approval with the first participant. Any thoughts on what might be going awry here? Thanks 

i am using adobe acrobat developer acc and i am trying to put a form fileds in a uploaded document and i think i will use to achive these by calling CreateNewWidgetWithCounterSigners.json ,  wheather this method is correct or not.if not ,please guide me with your essentials.

To sign a PDF document in Adobe Acrobat, I created a Digital Signaure and added it to the file and saved it as an attachement. I then went to my email browser to send it as an attachent. When clicking send, I get the following password request: "Mail wants to sign using key "privateKey" in your keychain" This never happened before and I suspect something got changed when creating the Adobe Digital Signature in Adobe Acrobat. In my apple KeyChain I do not have such a passord stored. This problem is only occuring on the email account on my laptop. It is not an issue on other device. Can anyone help please?

Does Adobe Sign currently support the Oauth Client Credentials flow?  I am getting a general/vague error ("Sorry, we are not able to process your request") when trying it with what I believe to be a valid request.  

Hi Team, I have created a agreement with prefill form fields (MergeFieldInfo).  Agreement is created successfully and it's status is set to "Waiting for prefill". While I am creating the agreement, I am passing the MergeFeildInfo, why is it still waiting on my side to prefill ?? Requirement:I want to bypass the "Waiting for prefill" status and it to be set to "Out for Signature" on agreement creation.   ThanksGoutham Bommu

Hi, When the agreement is signed by the signer, we are using Data Mapping to capture the inputs entered by the signer and get the below error once signed. The error is not coming while sending out the agreement.  Failed to retrieve form data from Adobe Acrobat Sign, any Adobe Acrobat Sign Form Field mapping will be skipped: echosign_dev1.EchoSignDataMapping.EchoSignException Unable to retrieve FormData from EchoSign: Unable to retrieve FormData from EchoSign: Adobe Acrobat Sign API returned error: : 401 : {"code":"INVALID_USER","message":"Invalid user ID or email provided in x-api-user header"} (echosign_dev1) 980 

While tesing API capabilities, using a single-page test PDF, i can successfully create a transientDocument and and agreement in AUTHORING state, but immediately after receiving the success message recieve an email indicating the system was unable to create the agreement as the document exceeds the page limit of 100.  Investigating the status of the created agreement shows the state as CANCELLED.

I was looking at the release notes and saw support for postSendOption.redirectURL in the POST /agreements/{agreementId}/ endpoint. I don't understand how to use this though. I've tried passing the param as {postSendOption: {redirectUrl: <myUrl>}} to POST /agreements but that doesn't seem to work.Its also worth nothing that the REST API v6 documentation (https://secure.na1.adobesign.com/public/docs/restapi/v6#://) makes no mention of this parameter.Also the only endpoints listed in the REST API docs are POST /agreements and PUT /agreements/{agreementId}. What am I missing?

in our software an order is created based on Json data. We intend to transform this document to a PDF file with an especial template. Then we want to show that PDF file on a website. Next, customer review the order and sign it by Adobe Acrobat Sign in the case of confirmation. Finally, the signed version of the PDF file should be emailed by clicking the OK button.Programming Language: C#Technology: .NetCore

Hi, New developer account for Adobe SignUsing postman, I can upload and create a transient document; the PDF is 1 page long.When I move onto generate the agreement, I get a valid ID backApprox 3 seconds later I get the following error returmed We were unable to create your agreement [DEMO USE ONLY] Test because your document Application1.pdf exceeds your page limit of 100. I dont understand, I ahev tried multiple .PDF files, each of which create a transientDocumentId when I first submit and then the id returned from the Agreements post. Any thoughts?

Hi Support,I do have some quieres which I need help from you.I am trying to implement Above Acrobat Sign Api for which I am following link https://secure.na1.adobesign.com/public/static/oauthDoc.jsp.I have successfully able to generate "Code" for Authorize request. After that trying to get Access Token with Access Token Request, as I make post request it return "Error: Request Security Violation at /" Also, I have tried "https://helpx.adobe.com/sign/kb/how-to-create-access-token-using-postman-adobe-sign.html"and follow every single steup and end up with  Please let me know if I am missing something.After all Thanks in Advance. 

When a pdf document is signed by a recipient a blue date/time stamp is added underneath the signature. I'd like to be able to reposition this to another part of my pdf and keep the signature where it is. Is that possible either via the API or other means?

Hi, New developer account for Adobe SignUsing postman, I can upload and create a transient document; the PDF is 1 page long.When I move onto generate the agreement, I get a valid ID backApprox 3 seconds later I get the following error returmed We were unable to create your agreement [DEMO USE ONLY] Test because your document Application1.pdf exceeds your page limit of 100. I dont understand, I have tried multiple .PDF files, each of which create a transientDocumentId when I first submit and then the id returned from the Agreements post. Any thoughts?

I am required to develop a solution (website) that would allow a user to sign 100 PDF documents at once using the Acrobat Sign API. For now, let's assume that all the documents have a signature field on a known page. Is this possible?All I could find in the API documentation was the misleadingly named megaSigns (REST API — Document e-signature Software — Acrobat Sign ) but, as far as I can tell, it is actually a megaSend, as in, you use it to send documents out for signing in bulk, not actually sign the documents in bulk.

Hi,We have registered an application under “API Applications” and got the “Client Id” and “Client Secret” to access the API. But we stuck up in the initial stage itself to get the “Authorization Code”.Based on the following example, we try to get the authorization code with all the needed parameters using the following URL.https://secure.eu2.adobesign.com/public/oauth/v2?redirect_uri=https://secure.echosign.com/public/login&response_type=code&client_id=C**********A-*****************S&scope=user_login:selfAs mentioned in the above screenshot from the document, in the response we neither get the authorization code nor the error. Instead we receive a HTML of the following page.Can anyone please help me out to get the authorization code?

I have successfully uploaded a pdf document then created an agreement using the POST /agreements endpoint. At this point I want to add a custom signature form field to the agreement which I do successfully using the PUT /agreements/{agreementId}/formFields and passing up the location area where is signature box is meant to be, this also works succesfully and can be seen via the receivers Adobe Sign account. The form has a 2nd 'Email:' and 'Signature:' fields placed at the bottom of the pdf that the receiver can click to add their signature. How do I prevent both of these from being added? The signature form fields I am adding via the PUT request is all I want. Thanks. 

Hi, We are trialing the Adobe sign Pro tier for a sign solution for our company. This is the highest tier that I can find yet I can't connect the account to Integromat/Make. When setting up the connection I get the error "[access_denied] User cannot authorize application because it is UNCERTIFIED"I have searched high on low and can't any information on connecting Sign. Even finding any API information is extremely troublesome. In a world where everything is connected via native integrations or services such as Integromat/ Make I can't believe a company so big such as Adobe is making the use of their API so hard. As it stands we won't be using Adobe Sign as a solution for our company for this reason we will be looking into other e-sign services that allow easy access to their API. 

{"fileInfos":[{"transientDocumentId":"3AAABLblqZhABbunFXbYVw8ebYEaV3f9UZJxA4IapuypniVDjOHtUyLfnLlxmFTDo7PXZ9_fmPcoB69gLmYpfZXi36qR33MLGskxDIF0IoejLPjez-8thrM2lgm6ozFXLKyCoSfY5Wl2H1t_VmetX0libk6Jw8Fi3xBJJIzK-lfek21ddtWN8y638Fr2dRFvQkD30dzDjuLMYr_zbR9A5ssrsVP43p6oOxKL1-PIv5zz8j3iQmzqZg4RxF974K8lOs8Vk87ZBOsOx7pxPrITV5yqxIXu9rPxa9R7YXjS253zgIl7oyWW-MyYN5ow24jut-9sms_yH1sKHFz5m7myHZJoS0wO-1w2ptjA0HUo5QaTX2DGVPGRaGA**"}],"name":"AdobeEsign","participantSetsInfo":[{"memberInfos":[{"email":"jjohn@tcasonline.com","name":"Jinson John"}],"order":1,"role":"SIGNER"}],"signatureType":"ESIGN","state":"IN_PROCESS"} I have used the above JSON in the REST API and I got the response (agreementid) but when I use the same JSON in REST Client it's showing  {"code":"INVALID_JSON","message":"An invalid JSON was specified"} ServicePointManager.Expect100Continue = true;ServicePointManager.SecurityProtocol = SecurityProtocolType.Tls12;string baseUri = string.Format("https://api.eu2.adobesign.

I've developed a web app that utilises the Adobe Acrobat Sign API. I've POSTed my .pdf to the transientDocuments enpoint:https://api.eu1.documents.adobe.com/api/rest/v6/transientDocuments Then create and agreement with the transient document id, recipient email (my own Adobe account) and other relevant information in the JSON packet and POST that to the endpoint:https://api.eu1.documents.adobe.com/api/rest/v6/agreements At this point the document is now in listed in my account under the manage tab > waiting for you. It has the options of 'Open', 'Fill' and 'Add Notes'. At this point I don't receive an email for the document being posted. I want to add a signature and sign it but there is no sign option and clicking 'Fill' shows a spinner briefly then does nothing. How can I esign the document after it has been uploaded?How do I ensure I receive an email notification that the document has been uploaded?How can I get a confirmation when it is esigned? Tha

Hi, I want to know what the format of the tag used to tag Auto Seal in the document while sending for signature.We are integrating with Adobe Sign using API 6.0 and we could provide participantset with sea identifire. Hwever could not find any reference regarding how to tag seal in the document.

I would like to add in an additional signer to an existing web form. How can I do this?

Does anyone have any experience with cloning one group to another group?  We qualified one group with the configuration set to use biopharm settings as the "gold standard" and would like to use that "gold standard" group to create additional groups for other departments.  Any changes would follow a change control procedure and testing would be performed in the "gold standard" and then manually migrated to the other groups.  We have been told there is no way to do that except for Adobe personell to perform this in the backgroud.  This is not a viable long term solution.  Looking for others that have the same issue and possible solutions.  Thank you.

Is the Adobe Acrobat Sign service experiencing stability issues recently / today? I'm using the API to request an Access Token. After having received a code from an Authorization Request I am now using postman to request a Beaer Token. I have configured my Post request in Postman in accordance with the api documentation and receive a 500 error when sending the request. Postman returns:Sorry, we were not able to process your request.Please try again later.If this error persists, please contact support.  

We would like to dynamically create a fillable PDF, where several field values need to be entered by the person creating the document, then we would like to send it to an applicant who would fill in a further set of fields and sign it. I presume this is the fill and sign feature? Is that an example of it anywhere?