Skip to main content

Get one of the calling bank's onboarding cases

GET 

/v1/onboarding-cases/:case_id

Returns the onboarding case, its saved configuration and its readiness checklist.

Required scope: connector:onboarding:read. The bank is taken from the bank_memberships claim of your access token. A case that does not exist or belongs to another bank returns 404.

State refresh. When the case has an activation_operation_id, this call first reads that operation and brings the case state up to date (AWAITING_APPROVALS, PROVISIONING, ACTIVE, REJECTED or FAILED). Poll this endpoint to follow the case after submission. The case becomes ACTIVE only after the activation operation succeeds and every identity provisioning job (staff memberships, M2M workloads) has completed; until then it stays PROVISIONING.

Readiness. readiness.ready_for_review is true when all three signing targets and the encryption target are VERIFIED, at least one staff member has the bank-admin label, and readiness.webhook_ready is true. These are exactly the checks POST .../submit-configuration enforces. maker_present, checker_present and readonly_present are informational only.

This response also includes bank_portal_route_code, the code used to build your bank's private Bank Portal login URL.

Request​

Responses​

Onboarding case, configuration and readiness status.