Customer Application Create

POST

https://live.tradovateapi.com/v1/customerApplication/create

POST

/v1/customerApplication/create

$ curl -X POST https://live.tradovateapi.com/v1/customerApplication/create \
>      -H "Authorization: Bearer <token>" \
>      -H "Content-Type: application/json" \
>      -d '{
>   "userId": 12345,
>   "accountType": "Customer",
>   "legalStatus": "Corporation",
>   "startDate": "2024-01-15T09:30:00Z",
>   "applicationStatus": "ApprovedApplication",
>   "archived": false
> }'

200Successful

1 {
2   "userId": 12345,
3   "accountType": "Customer",
4   "legalStatus": "Corporation",
5   "startDate": "2024-01-15T09:30:00Z",
6   "applicationStatus": "ApprovedApplication",
7   "archived": false,
8   "id": 98765,
9   "rejectReason": "IncompleteApplication",
10   "additionalNotes": "Missing required documentation for compliance review.",
11   "accountId": 54321,
12   "rejectDate": "2024-01-20T14:45:00Z",
13   "clearingHouseId": 67890,
14   "autoApprovalType": "PreApproved",
15   "duplicate": false
16 }

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).

### Create a customer application entity. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** 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`](/api/rest-api-endpoints/users/start-customer-application) instead, which creates the application together with its workflow state and is the entry point for [`submitApplicant`](/api/rest-api-endpoints/users/submit-applicant), [`prepareAgreementDocuments`](/api/rest-api-endpoints/users/prepare-agreement-documents), and [`signAgreementDocuments`](/api/rest-api-endpoints/users/sign-agreement-documents). 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`).

Authentication

AuthorizationBearer

Bearer authentication of the form Bearer <token>, where token is your auth token.

Request

This endpoint expects an object.

userIdlongRequired

accountTypeenumRequired

Customer, Employee, Giveup, House, Omnibus, Wash

legalStatusenumRequired

Corporation, GP, IRA, Individual, Joint, LLC, LLP, LP, PTR, Trust

startDatedatetimeRequired

applicationStatusenumRequired

ApprovedApplication, EscalatedToAML, InAMLReview, InComplianceReview, InReview, PendingApplication, PendingReview, RejectedApplication, ReviewCompleted

archivedbooleanRequired

idlongOptional

rejectReasonenumOptional

AMLWatchlist, AutoDenied, CIPCannotVerifyIdentity, ComplianceRejectionHighRisk, DuplicateApplication, IncompleteApplication, OtherRejectReason, PreviousBankruptcy

additionalNotesstringOptional<=8192 characters

accountIdlongOptional

rejectDatedatetimeOptional

clearingHouseIdlongOptional

autoApprovalTypeenumOptional

AutoApproved, PreApproved

duplicatebooleanOptional

Response

CustomerApplication

userIdlong

accountTypeenum

Customer, Employee, Giveup, House, Omnibus, Wash

legalStatusenum

Corporation, GP, IRA, Individual, Joint, LLC, LLP, LP, PTR, Trust

startDatedatetime

applicationStatusenum

ApprovedApplication, EscalatedToAML, InAMLReview, InComplianceReview, InReview, PendingApplication, PendingReview, RejectedApplication, ReviewCompleted

archivedboolean

idlong

rejectReasonenum

AMLWatchlist, AutoDenied, CIPCannotVerifyIdentity, ComplianceRejectionHighRisk, DuplicateApplication, IncompleteApplication, OtherRejectReason, PreviousBankruptcy

additionalNotesstring<=8192 characters

accountIdlong

rejectDatedatetime

clearingHouseIdlong

autoApprovalTypeenum

AutoApproved, PreApproved

duplicateboolean