Submit Applicant
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: No endpoint-specific limit
Submit the applicant’s personal, financial, and regulatory details for a customer application. Call this after starting the application with startCustomerApplication, using the returned application id as customerApplicationId.
Provide at least one applicant object matching the application’s legal status:
individual — for Individual and IRA applicationsjointApplicant — for the second applicant on Joint applicationscorporate — for entity applications (Corporation, LLC, LLP, LP, PTR, Trust)The request is rejected if all three applicant objects are empty. Only the primary applicant’s login can submit or change applicant details.
Set dryRun to save the applicant details without finalizing the submission — useful for persisting progress while the applicant is still filling out the application.
A successful response returns the created applicant record ID (individualApplicantId or corporateApplicantId). The response can also include duplicateMetadata — if duplicateFound is true, the details matched an existing application or account, and the metadata references the conflicting customerApplicationId or accountId.
Business Rules
The submission is rejected when:
Hedger margin type — only Speculator accounts are supported.debtorInBankruptcy).birthDate is missing for an individual applicant.country does not match the user’s country of residence (applies to applications in certain jurisdictions).Common Failure Scenarios
customerApplicationId does not reference an existing application.individual, jointApplicant, and corporate are empty.Error Messages
Next Steps
submitCustomerApplicationDocument.prepareAgreementDocuments.