Customer Application L Dependents

GET

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

GET

/v1/customerApplication/ldeps

$ curl -G https://live.tradovateapi.com/v1/customerApplication/ldeps \
>      -H "Authorization: Bearer <token>" \
>      -H "Content-Type: application/json" \
>      --data-urlencode masterids=10234,20456,30987

200Retrieved

1 [
2   {
3     "userId": 10234,
4     "accountType": "Customer",
5     "legalStatus": "Corporation",
6     "startDate": "2023-11-20T14:45:00Z",
7     "applicationStatus": "ApprovedApplication",
8     "archived": false,
9     "id": 4587,
10     "accountId": 78901,
11     "clearingHouseId": 345,
12     "autoApprovalType": "AutoApproved",
13     "duplicate": false
14   },
15   {
16     "userId": 20456,
17     "accountType": "Employee",
18     "legalStatus": "Individual",
19     "startDate": "2024-02-10T08:15:00Z",
20     "applicationStatus": "RejectedApplication",
21     "archived": true,
22     "id": 4590,
23     "rejectReason": "CIPCannotVerifyIdentity",
24     "additionalNotes": "Identity verification failed due to mismatched documents.",
25     "accountId": 78945,
26     "rejectDate": "2024-02-15T10:00:00Z",
27     "clearingHouseId": 346,
28     "autoApprovalType": "PreApproved",
29     "duplicate": false
30   },
31   {
32     "userId": 30987,
33     "accountType": "Giveup",
34     "legalStatus": "LLC",
35     "startDate": "2024-03-01T12:00:00Z",
36     "applicationStatus": "InReview",
37     "archived": false,
38     "id": 4595,
39     "accountId": 78999,
40     "clearingHouseId": 347,
41     "autoApprovalType": "AutoApproved",
42     "duplicate": false
43   }
44 ]

List the customer applications for multiple users.

Available to: All authenticated users

Environments: Demo, Live

Rate Limit: No endpoint-specific limit

Returns every CustomerApplication associated with the users identified by the masterids query parameter (a comma-separated list of user IDs). This is the batch form of customerApplicationDependents — use it to sweep application status across many users in one request, such as checking the onboarding progress of your organization’s members. Match each returned application to its user via the userId field.

Each returned application carries its userId, accountType, legalStatus, startDate, and applicationStatus (PendingApplication, ApprovedApplication, RejectedApplication, PendingReview, InReview, InComplianceReview, ReviewCompleted, EscalatedToAML, or InAMLReview), plus accountId, rejection details, clearingHouseId, autoApprovalType, duplicate, and archived when applicable. See customerApplicationItem for field details.

Results are scoped to the entities the caller is permitted to see.

Common Failure Scenarios

The masterids parameter is missing or contains values that are not valid user IDs.
The access token is missing or invalid (returns HTTP 401).

### List the customer applications for multiple users. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** No endpoint-specific limit Returns every `CustomerApplication` associated with the users identified by the `masterids` query parameter (a comma-separated list of user IDs). This is the batch form of [`customerApplicationDependents`](/api/rest-api-endpoints/users/customer-application-dependents) — use it to sweep application status across many users in one request, such as checking the onboarding progress of your organization's members. Match each returned application to its user via the `userId` field. Each returned application carries its `userId`, `accountType`, `legalStatus`, `startDate`, and `applicationStatus` (`PendingApplication`, `ApprovedApplication`, `RejectedApplication`, `PendingReview`, `InReview`, `InComplianceReview`, `ReviewCompleted`, `EscalatedToAML`, or `InAMLReview`), plus `accountId`, rejection details, `clearingHouseId`, `autoApprovalType`, `duplicate`, and `archived` when applicable. See [`customerApplicationItem`](/api/rest-api-endpoints/users/customer-application-item) for field details. Results are scoped to the entities the caller is permitted to see. **Common Failure Scenarios** - The `masterids` parameter is missing or contains values that are not valid user IDs. - 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.

Query parameters

masteridslist of longsRequired

List of User entity IDs

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