Customer Application Create

Create a customer application entity.

Available to: All authenticated users

Environments: Demo, Live

Rate Limit: No endpoint-specific limit

Insert a CustomerApplication entity record directly. This is the generic entity-create operation — it writes the record but does not run the account-opening workflow. To open an account, start the application flow with startCustomerApplication instead, which creates the application together with its workflow state and is the entry point for submitApplicant, prepareAgreementDocuments, and signAgreementDocuments.

The request body is the entity itself. Required fields:

• userId — the user the application belongs to
• accountType — Customer, Employee, Giveup, House, Omnibus, or Wash
• legalStatus — Corporation, GP, IRA, Individual, Joint, LLC, LLP, LP, PTR, or Trust
• startDate
• applicationStatus — PendingApplication, ApprovedApplication, RejectedApplication, PendingReview, InReview, InComplianceReview, ReviewCompleted, EscalatedToAML, or InAMLReview
• archived

Optional fields include accountId, clearingHouseId, rejectReason, rejectDate, additionalNotes, autoApprovalType, and duplicate. When rejectReason is OtherRejectReason, additionalNotes must be non-empty.

A successful request returns the created entity, including its assigned id.

Common Failure Scenarios

• A required field is missing.
• rejectReason is OtherRejectReason without additionalNotes.
• The caller does not have write access to the referenced user’s applications.
• The access token is missing or invalid (returns HTTP 401).