Create new terms and conditions for a signer
POST /v2/onboarding/agreements/terms| Tag | Description | Required | Type | Value restrictions |
|---|---|---|---|---|
| legalEntityName | legal entity name | Yes | String | |
| signerFirstName | signer’s first name | Yes | String | |
| signerLastName | signer’s last name | Yes | String | |
| signerEmail | signer’s email address | Yes | String | valid e-mail address |
| termsAgreementFormat | agreement format | Yes | String | docusign (anchorage format has been deprecated) |
| returnUrl | URL to redirect to once terms and conditions are accepted | No | String | |
| frameAncestorress | URL where the terms and conditions link should be embedded | No | String |
termsAgreementId is returned, which will be used in an end client onboarding application. A Docusign signed and timed url is also returned. A new signed URL is returned on each GET call as long as the terms are still IN_PROGRESS.Anchorage Digital supports Docusign’s Embedded Signing integration, which allows immediate signing within an app or website. Signed URLs are valid for 5 minutes (a Docusign limit that cannot be changed) and should be generated immediately before use. If a URL expires, request a new one with a subsequent GET call to the agreement endpoint. All agreements must reflect a status of
COMPLETE before submitting the full onboarding application. See Docusign embedded signing documentation for details.Changelog
| Date | Change |
|---|---|
| June 10, 2025 | Updates for new onboarding API payloads and flows |
| May 1, 2025 | Initial version |