Submit Applicant
Submit applicant details for a customer application.
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— forIndividualandIRAapplicationsjointApplicant— for the second applicant onJointapplicationscorporate— 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:
- The applicant selects the
Hedgermargin type — onlySpeculatoraccounts are supported. - The applicant reports a previous bankruptcy filing (
debtorInBankruptcy). - The applicant is under 18 years old, or
birthDateis missing for an individual applicant. - The applicant’s
countrydoes not match the user’s country of residence (applies to applications in certain jurisdictions).
Common Failure Scenarios
customerApplicationIddoes not reference an existing application.- All of
individual,jointApplicant, andcorporateare empty. - The caller is not the primary applicant on the application.
- The caller belongs to a reliance-agreement organization and cannot sign on behalf of customers.
Error Messages
Next Steps
- Upload any required supporting documents with
submitCustomerApplicationDocument. - Generate the agreement documents for signing with
prepareAgreementDocuments.
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Request
Response
Non-empty if the request failed