Yes I understand the probem, you have a fixed first participant and a fixed last partcipant and then a variable number of participants in between. The field assignment is derived from the index of particiants   Conditions are not allowed on initial and signature fields    Simplest solution is t try and have all variable signers be the last part, but business rules won't always allow for that. You could have multiple template catering for each possible scenario, but this adds up to a lot of templates. One option if you have a Sign account with access to workflow, is to use a workflow and tmake use of the 'Template defined field assignment' option.   See: https://helpx.adobe.com/sign/using/workflow-designer-signature-workflow.html   Another alternative would be to make use of the Sign api v6, but that may be a tad overkill. ... View more

it's configurable in Sign settings by a Sign account admin, but a lot will depend on how Sign has been licensed as well. ... View more

If you have a qualifying sign account, then you can make use of calculated fields, see my reply to this post: https://community.adobe.com/t5/adobe-sign-discussions/fields-that-repeat-information/m-p/12489834#M17743 ... View more

Webhooks Documentation in v6 you do not set a callbackurl when creating an agreement, you setup a webhook instead. ... View more

you sign account will be on a specific server, for example secure.eu1.echosign.com or secure.in1.echosign.com this needs to be reflected in the Oauth end point. The oauth documentation Adobe Sign, an Adobe Document Cloud Solution , may not be pointing to the same shard as you account. So instead of pointing to https://secure.eu1.echosign.com/public/oauth? you may need to update this to https://secure.na2.echosign.com/public/oauth? ... View more

probably, but no-one is going to tell for sure as SOAP has been deprecated for some time and no longer supported. Try and move all legacy to REST api  as soon as you can. ... View more

Can't telly you why, but there's no method to create user in V6, use v5 instead. ... View more

See Postman screenshots        When you move the mouse over the Key field in the second screenshot you get a dropdown at the end of this field to specify if it's a file or text you want to add. For Api v6 it's mostly the same just change the access-token header to 'Authorization' and prefix your access token with the word 'Bearer ' . ... View more

assuming you setup a dev account using the same email address as your forum user here, The webhooks have been created and are active, however each post request is met by a http 405 respone (method not allowed) From Wbehook Documentation How to respond to a webhook notification Adobe Sign performs an implicit verification of intent in each webhook notification request that is sent to the webhook URL. Every webhook notification HTTPS request contains the customer HTTP header called X-AdobeSign-ClientId. The value of this header is the client ID (Application ID) of the application that created the webhook. We will consider the webhook notification successfully delivered, if and only if a success response (2XX response code) is returned and the the client ID is sent in either the HTTP header (X-AdobeSign-ClientId) or in a JSON response body with key as xAdobeSignClientId and value as the same client ID; otherwise, Adobe Sign will retry to deliver the notification to the webhook URL until the retries are exhausted. so to be clear to register the webhook is a Get request, but once active the webhook then makes POST request to deliver the payload. ... View more

For starters use the documentation here REST API — Document e-signature Software — Adobe Sign Note this link goes to the eu1 server. update the url to the same server as your account (eg na1 or na2 or in1 etc) the article has a mistake in that there's no recipientInded in v6 but rather an 'Assignee' property which works quite a bit different to an index (see documentation) easiest thing to do is to use the webportal to send an agreement with the fields you wan to add dragged on to it. The via the manage tab and history>audit report get the transactionID. This transactionID is also the AgreementID v6 api uses. use this agreementID in a call to get /agreements/{agreementId}/formFields​ you can use the response as a template for your put call. (but do add the assignee property) ... View more

your access token needs to have at least group or account scope. The use the x-api user header to create agreements as a different user in the same group/account. ... View more

If the email server of the participant email domain sends a bounce back message, this is captured in an event. So if polling look for the bounc event. If using webhooks you can suscribe to a bounce event. ... View more

1) Yes with v5 as well you can end up calling get /signingurl before the agreement is ready. In which case simply retry until success. You may want to consider checking the status of an agreement first before calling the get signurl, as agreements sometimes fail to get created successfully and you may end up retrying to get the signingurl forever 2) v5 REST API — Document e-signature Software — Adobe Sign ... View more

Opportunity is not a custom object, which this tutorial is about. Though what you are looking for is part of this KB article: Adobe Sign for Salesforce Templates and Data/Merge Mapping ... View more

Can only suggest some troubleshooting here If you have something like SOAPUI it may help speed up testing. first try with a different file source, instead of a url, upload a file or use a librarydoc id instead. If no errors, ensure your file is publicly accessible from that link. If an error still occurs, there's like a different issue in the request. For example if you set senderInfo, try nilling that. Without a senderinfo the user who owns the api key will be assumed the sender. finally if still no luck see if if you can do the request in REST api on the swagger pager here: REST API — Document e-signature Software — Adobe Sign ... View more

manual intervention with oauth would be a one off. Once you have the first access token you should also have a refresh token, which can be used to programmatically refresh the access token when needed. ... View more

2 options come to mind. One you split it in 2 agreements. 1st agreement is send to the recipient and you set the recipient as a 'Certified recipient role'. This means you still use the Adobe Sign audit trail for tracking. After they complete (by simply receiving) you'd get a webhook update and then count to 7 days before sending a new agreement, this time using the Signer role for the sender. You would include an expiry date set a 7 days to ensure the second agreement is signed within that time frame. You can use the completed document from the first agreement as the source for the second agreement. Though technically there's still the issue of having 2 documents. option 2 would be to contain it within one agreement. You'd create an agreement with 2 recipients recipient 1 same as before, the intended client with a certified recipient role, second recipient a delegator role, or a placeholder email. Once recipient 1 confirms receipt, again wait 7 days, then use the api to replace recipient 2 with the intended signer. You can also use the api to set a new expiration date. 3rd option comes to mind is where you ask Support to turn off emails created by Sign. In this case create an agreement again with two recipients. In this case it can be the same email address, but again recipient 1 is the Certified recipient and recipient 2 the signer. The first recipient can receive the Sign email as per usual, but any following recipients would not get any Sign generated emails. Again once receipt is confirmed, you wait 7 days and now retrieve the signing url and distribute this url in some way to the intended signer, but there's no easy delay parameter as such. ... View more

check your url and ensure the pdf is served from a secure https link and not regular http. ... View more

there's no real workaround here. Perhaps the best thing to do is to fix the point size to 10 and limit the number of characters one can enter. Though for such text to look the best, you'd need to add these values in the source document and upload that instead if possible. ... View more

I assume you configured you oauth app as a partner application. By default such apps are uncertified and your customer will need to allow uncertified app in their own adobe sign account. (it's in the security settings I believe). it's possible to get your application certified, for that contact support first. or visit this widget Adobe Sign, an Adobe Document Cloud Solution ... View more

click more (on the right hand side) and convert to Adobe Sign form. This changes the form tools to Adobe Sign form tool including the initial fields. ... View more

I'm not entirely sure but going by this, the answer would be no: Icons and web logo guidelines | Adobe I would say that the logo is used by default in Adobe Sign agreement and emails already. ... View more