Error
White Label App
Get Applications
Retrieves a user’s existing financial-service account applications
GET
Error
Use this endpoint to check whether a user already has an application in progress or has already been onboarded, before you start a new White Label App (WLA) onboarding flow. Send a GET request to
If the user has more applications than fit in a single page, use the
/applications with the user’s ID; the response includes every application submitted for that user, ordered by created_on in ascending order.
Reasons to call this endpoint include:
- Resuming an interrupted signup: Check for an existing application in the
KYCstatus before redirecting the applicant to start over, then reuse thekyc_urlfrom that application instead of submitting a duplicate. - Displaying application status in your app: Poll this endpoint to show the applicant where they stand, as a fallback for cases where you cannot process outbound application events.
- Preventing duplicate submissions: Check for any non-final application (
SUBMITTED,KYC, orMANUAL_REVIEW) for the user before you submit a new one.
active_only to false if you also need to see applications in a final status, such as APPROVED, REJECTED, or EXPIRED.
If the specified user has no applications, the response returns an empty
applications array rather than an error.next_cursor value from the response as the cursor parameter in your next request to page through the rest.Authorizations
Token used to verify user identity and also authorize user to use service.
Query Parameters
Partner-provided user ID to filter applications by.
Indicate if only active applications should be returned.
An active application is one that has a status other than APPROVED, REJECTED, or EXPIRED.
Maximum number of items to return. If not present, no limit should be applied.
Required range:
1 <= x <= 100Cursor to a specific position in the results. If not present, the first page should be returned.
Example:
"eyJpZCI6IjEyMyJ9"