Sign Agreement Documents
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Response
Non-empty if the request failed
Bearer authentication of the form Bearer <token>, where token is your auth token.
Non-empty if the request failed
Available to: All authenticated users
Environments: Live
Rate Limit: 10 requests per hour, 30-second back-off, counts all requests
Record the applicant’s signature on the agreement documents prepared for a customer application. Call this after generating the documents with prepareAgreementDocuments.
All fields are required:
customerApplicationId — the application being signed, from startCustomerApplicationagreementIds — the AgreementDocument entity IDs to sign; list them with agreementDocumentDependentsagreementReadConfirmation — must be true, confirming the applicant read the agreementssignature — must match the applicant’s full name exactlydate — must be today’s date (Central Time)For individual, joint, and IRA applications, the signature is validated against the applicant’s first and last name; on joint applications, a co-applicant login signs with the joint applicant’s name. For entity applications, the signature must match the full name of the primary contact.
A successful response returns a successHashCode.
Common Failure Scenarios
customerApplicationId or any of the agreementIds does not reference an existing entity.submitApplicant and prepare the documents before signing.Error Messages