List missing fields

Returns the fields and documents still required to complete onboarding for the selected account. Provide the level query parameter to scope the result to one verification level; a level-scoped result may also include a short-lived token for finishing the remaining checks in the embedded onboarding flow. Only a Banking level-scoped read may run verification again: when Banking needs an update (UpdateRequired) with no fields left to collect and no verification flow is assigned, a read by a signed-in Person whose credential grants users.identity-verification:write and who has Write authority on the selected account runs Banking verification and returns the token for the step that is now required. Banking verification status may change as a result. Tax and Enhanced reads, Banking reads in any other status, and reads by API keys, ServiceAccounts or impersonated sessions never run verification; use the trigger verification endpoint and fetch missing fields again. If the Banking re-run is not authorized or fails, the read still succeeds without a token. Before a verification profile exists, a level-scoped read succeeds with empty field and document arrays; that empty pre-profile snapshot does not mean verification is complete. During any impersonation, missing fields and documents remain available, but root and country-profile onboarding tokens are neither issued nor returned; the customer must complete verification themselves. The no-login principal Stakeholder Tax path returns missing fields and documents without issuing an interactive identity onboarding token.

Recent Requests
Log in to see full request history
TimeStatusUser Agent
Retrieving recent requests…
LoadingLoading…
Query Params
string
enum

Verification level to scope the result to. When omitted, the response aggregates missing fields across all levels and carries no onboarding token.

Allowed:
Headers
string
^(?:[A-Za-z0-9_.]{22}|[a-f0-9]{24})$

Select the Account for an Account-scoped operation. A direct ServiceAccount API key MUST supply this header, and the target must be within the ServiceAccount owner's or Authorization grant's Account boundary. A Person bearer may select an Account on which it has an active Stakeholder, and an Account session may select its bound Account (or a descendant only when the session explicitly includes descendants).

string
enum
Defaults to application/json

Generated from available response content types

Allowed:
Responses

Language
Credentials
Bearer
JWT
LoadingLoading…
Response
Click Try It! to start a request and see the response here! Or choose an example:
application/json
application/problem+json