Customer Application Dependents

### List the customer applications for a user. **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 user identified by the `masterid` query parameter. Use this to find a user's applications and their current state — for example, to locate the `customerApplicationId` for the application-flow endpoints, or to check whether a user already has an application before starting a new one with [`startCustomerApplication`](/api/rest-api-endpoints/users/start-customer-application). 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. A user with no applications returns an empty array. To list applications for several users in one request, use [`customerApplicationLDependents`](/api/rest-api-endpoints/users/customer-application-l-dependents). Results are scoped to the entities the caller is permitted to see. **Common Failure Scenarios** - The `masterid` parameter is missing. - The referenced user does not exist or is not visible to the calling user. - The access token is missing or invalid (returns `HTTP 401`).