Customer Application Item
Fetch a single customer application by ID.
Available to: All authenticated users
Environments: Demo, Live
Rate Limit: No endpoint-specific limit
Returns the CustomerApplication entity identified by the id query parameter. Use this to check an application’s progress through the account-opening flow — for example, after starting it with startCustomerApplication (the application flow endpoints run on the Live environment).
Each application carries the userId it belongs to, its accountType and legalStatus, the startDate, and the applicationStatus (PendingApplication, ApprovedApplication, RejectedApplication, PendingReview, InReview, InComplianceReview, ReviewCompleted, EscalatedToAML, or InAMLReview). Approved applications reference the created account via accountId; rejected applications carry rejectReason, rejectDate, and additionalNotes. The record can also include clearingHouseId, autoApprovalType (PreApproved or AutoApproved), duplicate, and archived.
To list a user’s applications instead of fetching one by ID, use customerApplicationDependents. To fetch several applications at once, use customerApplicationItems.
An application is returned only when the caller has read access to it; results are scoped to the entities the caller is permitted to see.
Common Failure Scenarios
- No accessible customer application exists for the supplied
id. - The access token is missing or invalid (returns
HTTP 401).
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.