Questions

Since November 2023, I can request signatures and send agreements out, but they do not show up on my All agreements list so I cannot track them, or send reminders or anything else. Please help.

In v6 rest API I tested agreement view (post) {    "name": "ALL",    "commonViewConfiguration": {        "autoLoginUser": true,        "noChorome": true,        "postSendOption": {            "redirectUrl": "https://127.0.0.1:8080"        }    }} but I responsed  {  "code": "INVALID_POSTSEND_REDIRECT_URL",  "message": "Specified post send redirect URL not in allowed list - https://127.0.0.1:8080"} How do I add the URL to the allowed list?

I would like to know more on adobe acrobat sign API  , I was looking out for a way to not store the documents in adobe cloud which are to be sent to get signed from the users . Is there a way we can achieve this. I have found out that all the 3 ways , Uploading the document and creating the transient id, or to create agreement with library id or using the URL  , it stores the document temporarily in adobe cloud , We prefer not to store the document on the adobe cloud.

I'm integrating the Adobe Sign API into an app I'm developing. One feature of my app is to view a list of all outstanding agreements. To do this, I need to hit the endpoint to grab all agreements for the account. As is mentioned in another post on this forum, there is no way to filter the results of the API call to grab all agreements. That being the case, I assumed the only way to reduce the results returned by that call is to delete any cancelled or completed agreements. Otherwise the list of agreements returned by that API will continue to grow over time and that API call will get slower and slower as it needs to request multiple pages of results and concatenate them. However, that doesn't appear to be possible either. At least, not without contacting Adobe support and requesting that they enable the delete API endpoint for your account. So I'd need to advise all users of my application to do that in order to prevent my app gradually getting slower over time. I'm not sure

How to filtered agreements by specific status (Ex: OUT_FOR_SIGNATURE or SIGNED) in REST API?Currentlly there is no specific query parameter to use to achive this requirement in GET /agreements.

Hi, I have a document whereby I require a checkbox to display an actual checkmark.  The reason I've put that in bold and italics is because I'm finding it so incredibly frustrating because Adobe Sign will not allow me to do this. I'm at the point of giving up and just printing, manually checking and scanning instead. The final document (once signed) is just displaying the checkbox filled in, with no actual checkmark. Can anyone help? I've attached a photo for demonstration (circled in blue): Many thanks in advance for any help!

1. Create an app     - Please refer to the attached OAuth configuration.JPG file below2. Add an Authorization Request link     - Please refer to the attached Add an Authorization Request link.JPG file below      - request url -> https://secure.na1.adobesign.com/public/oauth/v2?redirect_uri=https%3A%2F%2Fsmartx-10.emro.co.kr%2Flogin.do&response_type=code&client_id=CBJCHBCAABAADReTniekxk9bMo0u6m06G_w9ytucLZTr&scope=agreement_write&state=JZVMFE6WA7RJ4R2LS89O3. Request result    - Please refer to the attached request result.JPG file below     

I am using the Acrobat Sign API to send an agreement out for e signature as outlined in the docs here https://opensource.adobe.com/acrobat-sign/developer_guide/apiusage.html#sendforsigning but my integration uses https://secure.adobesign.com not the new https://secure.echosign.com url yet. I successfully went through the oath flow and successfully created the document in Adobe. It shows up on my Adobe Acrobat home screen under recent documents. However, when I choose the document and click ‘Edit’ in order to add signatures to request it redirects me back to the Documents home screen. I'm not able to add recipents and signature requests to the document. Previously, I have seen my new document under the ‘Legacy Drafts’ tab on the left and when I clicked 'Edit' I could add recipents and signatures. But in this particular test adobe account ‘Legacy Drafts’ is not in the left hand menu. Is this a licensing problem with my Adobe account (Acorbat for teams standard)? If it

I am trying to Integrate ServiceNow with Adobe Sign in API. While trying out the APIs I was unable to send the agreement to the user.  I am using the POST Workflow API from v5 documentation. When sending the request it returns status code as 201 along with the agreement ID. But on checking the agreement from the console in Adobe it shows that the agreement has gone into the cancelled state. Sharing the payload which I am trying to send in the request:{ "documentCreationInfo": { "fileInfos": [ { "name": "Test678", "transientDocumentId": "CBSCTBABDUAAABACAABAAmz9440zDqcqrifesKtxV2kVSkzMWTAG_izjHBb1RdDHQ3uD9h1X9HoB0ddvTn8kdzVSwHaD5F5tHimOUkjirTL_rOgbMmiNodmAXdiMv2zOjguzna0OboypDIyrk5QGcuI-9T6P9Fj1ULp6yjfRuu663w66WJUH08glkO--LZmg7RzPq5NC_uG9ovXyhvka5PnePIYUU59-8pRJUCE0I1yXSrgti0IFN-01-dFg7BP5P2fvBes3KpStOZ_3scJuzsWCjzIKPt-GO734h7ycLC3-AOlThIFCy4EYdfA9_vidlpFdtZjwNcxTFi-Z9210mhIwo2xNQ7s4_qSPXOl0JFqQ9m185n7G8mN3ghwWKvkI*", "mimeType": "application/pd

Hi,I tried to add form field to an agreement. I use PUT method:FormFields option is not available in V6 of REST API | Adobe Sign Answer is 200 everything is OK, but on the document the signature block is allways by default.

When creating an agreement in UI, there's an option to "Add Recipient Group", or to simply add individual recipients. When I'm creating agreements with the API, the recipients always show up as "groups" instead of just individuals. Here is a screenshot of the recipient list for an agreement I created in UI. Note that the recipients show up as "(Signer)": Here is a screenshot of the recipient list for an agreement I created with the API. Note that the recipients show up as "(Group)": For the API call, I'm just following the format specified in the REST API Reference and this sample. I can't find any other way of formatting the API request such that it specifies the recipients as individuals rather than groups. Is this a limitation with the API? 

Hi,We are using the Adobe Sign APIs for signing the documents. We also created Webhook in our account. We are getting notifications for the users who are added in our account but n0t getting notification for the users those are not added in our account.How can we get the webhook notifications for all the users. Thanks

I am integrating my app using Adobe Sign Api's and managing signing audit history on my app.  For Agreement Rejection case the webhook is sending the event details as an agreement reject event but the webhook response does not contain rejection reason .  In my webhook configuration i have selected all agreement events and in notification parameters I have selected agreement info, Agreement Document Info, Agreement Participient Info, Agreement Signed Info all.Can you please suggest  how to receive this.

I'm creating multiple Agreements from the same template (a LibraryDocument), with differences to some un-editable fields, like an "Active Date" field. These differences are met with the mergeFieldInfo property of the AgreementInfo. All of the Agreements are sent to the same single participant. The expected behavior is that when the recipient views the documents of one of those Agreements, anAGREEMENT_DOCUMENTS_VIEWED webhook event for that agreement is sent. Instead, a AGREEMENT_DOCUMENTS_VIEWED event is sent for ALL the agreements sent to that participant that are created from the same template. Even AGREEMENT_WORKFLOW_COMPLETED events are fired for all agreements, meaning the agreements are all marked SIGNED, even though the participant has only viewed/signed ONE of them.  How do I ensure that these Agreements are treated as separate Agreements? Do I need to create a new LibraryDocument for each Agreement that is sent, to use as a template

I think it would be very helpful if there was a signing option added that was "Send/Return for revision" in addition to the existing option Decline to Sign. This would be helpful because it could be returned, erase any existing signatures and upon revision, the document could be rerouted for signatures.  Decline to sign requires that the creator start from scratch and reupload and place fields. 

Dear Users,   We are pleased to announce a valuable resource to streamline your experience with Adobe Acrobat Sign for Salesforce – our newly launched FAQ page!   Visit the Acrobat Sign for Salesforce FAQ page to access comprehensive answers to various queries, allowing you to navigate and enhance your experience with the package.   Explore the FAQ page today for an elevated user experience. Empower yourself with knowledge and maximize your Acrobat Sign for Salesforce package.

I have created an account and opted Adobe Pro (free trail for 7 days). Now I am trying to test  signing  a document having signle page PDF. While sending the agreement detials for Adobe Sign (Status: AUTHORING) getting error message and email mentioning that "We were unable to create your agreement Test because your document Single Page Agreement_pdf.pdf exceeds your page limit of 100."This is the very first document which I sent after creating the Account.I am testing the signing flow through our application which is integrated with Adobe Sign.  Pls let me know why we are getting this error and how can we remove this.

I am developing an integration with Adobe Sign for my application and intend to pilot it with a client who is already an existing Adobe Sign Enterprise customer. My Sign API app's status is active and the domain is "PARTNER" (access to any authorized Adobe Sign account). While the benefits of being on the App Exchange are of interest, I have a greater need to launch this integration for this one customer first. Will I be able to use my integration through my app with this existing Adobe Sign Enterprise account while the certification is still pending, or am I required to complete certification for any usage outside the developer account?

Is it possible to send multiple agreements with mergefields looking at the same object in salesforce as one agreement? I have a scenario where I need to send an agreement comprised of multiple templates as one agreement. We are trying to 'build' a large agreement by pulling in multiple agreement templates and sending at once. Issue is-when trying to add the files the merge fields come over as text and not the information as related to the object they should be referencing. Only the original template is correct.

The scenario is as follows:We host a platform with multiple usersWe would like our users to sign agreements with each other via our Adobe Sign accountWe are not part of the signed agreementsOur users do not have an Adobe Sign account themselvesOur ideas is:User A uploads a PDF file (i.e. a contract that has to be signed by User A himself and User B)We create an Adobe Sign Web Form / Widget with this PDF file Important: User A should now be able to add any signature fields they wish to the PDF via the Adobe Sign Web Form without requiring an Adobe Sign account on his own. For testing, we created the Web Form via REST API and set User A as the initial participant. The Web Form itself is set to the AUTHORING state. But, upon embedding the widget, in order to edit/add form fields, User A is prompted to sign in with his Adobe Sign account. How can we let User A add the required signature field(s), finish the web form (so it becomes ACTIVE) and subsequently send

Hi Team, I know we can create an agreement using adobe web portal where we are allowed to add the label and the multiple signatures on a specific position on a particular page. I want to do the same process using api for creating Agreement. Through API I want to allow a specific signer to sign at a position. like If I have 2nd signer for a agreement an If I want both signers to sign in different different locations and on one signer's location is one page(2), The other singers to sign another page (4) I don't want to allow other signer to sign. Then How can I do the same through api. I posted following Json. But not working{ "fileInfos": [ { "transientDocumentId": "{{transientDocumentId}}" } ], "name": "RENTAG TYPE 2", "participantSetsInfo": [ { "memberInfos": [ { "email": "xxxxx@gmail.com", "name": "xxxx s" } ], "orde

Hello, I have the latest version of Adobe and the Combine file options disappeared when I selcct multiple PDFs and right click. Can someone please urgently help me?

I am looking for a way to send a PDF for signature using Adobe ESign API and an authentication mechanism using a PIV Card.I am supporting a project  for a client and we are looking for a way to do the Adobe E-Sign the recipient of the document will be authenticated using a PIV card. Can you please provide me with pointers to this solution?

I have a JObect like below: {"fileInfos": [{ "transientDocumentId":"123#","label": "label for Doc 1"}],"name": "JaneDOE_VOE","participantSetsInfo": [{"memberInfos": [{"email": "abc@gmail.com"}],"order": 1,"name": "Signer - one","role": "ACCEPTOR"}],"signatureType": "ESIGN","externalId": {"id": "NA2Account_9/19/2023"},"state": "IN_PROCESS"} I want to convert this JObject to AdobeCreationInfo data type.

Hi, We need to integrate Adobe Sign API with our application.We have followed the instructions provided in the developer_guide "https://opensource.adobe.com/acrobat-sign/developer_guide/gstarted.html".But there is no option "API Application" to create an application in our account.There are only two options available in the left side menu.     API Information     API Request LogPlease guide me how to get the option "API Application" enabled in our account?