Customer Application Items

### Fetch multiple customer applications by ID. **Available to:** All authenticated users **Environments:** Demo, Live **[Rate Limit](/overview/core-concepts/rate-limits):** No endpoint-specific limit Returns the `CustomerApplication` entities identified by the `ids` query parameter (a comma-separated list of entity IDs). This is the batch form of [`customerApplicationItem`](/api/rest-api-endpoints/users/customer-application-item) — use it to check several applications in one request instead of one call per ID. 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. To list applications by user instead of by application ID, use [`customerApplicationDependents`](/api/rest-api-endpoints/users/customer-application-dependents) or [`customerApplicationLDependents`](/api/rest-api-endpoints/users/customer-application-l-dependents). Results are scoped to the entities the caller is permitted to see; IDs the caller cannot access are not returned. **Common Failure Scenarios** - The `ids` parameter is missing or contains values that are not valid entity IDs. - The access token is missing or invalid (returns `HTTP 401`).