Get onboarding status
Returns the onboarding status of a business entity, including uploaded documents and each representative’s KYC status in the representatives array. The top-level kyc_status reflects the primary representative.
Authorizations
Your Meow API key, sent in the x-api-key header for authentication.
Path Parameters
Response
Successful Response
Public ID of the onboarded business entity, stable across the onboarding lifecycle and matching the entity_id used in the Customer API, MCP, and webhook payloads.
Current onboarding status.
pending_document_upload, pending_user_action, submitted, under_review, approved, rejected Legal business name.
ISO 8601 timestamp of when the entity was created.
ISO 8601 timestamp of when onboarding was last updated.
Documents uploaded during onboarding.
Identity verification status of the primary representative. After you submit KYC data or they complete verification, this moves to pending and resolves on its own; poll it to track progress. action_required means their verification needs another step from them (for example, a document): create a link with POST /entities/{entity_id}/representatives/{representative_id}/verification-link and share it so they can finish. See representatives for every representative's status.
not_started, pending, action_required, approved, rejected How this entity was onboarded (e.g. api, smb, partner).
api, smb, mcp, partner What you must do next: the current onboarding step, the items still missing for it, and whether the application is ready to be submitted for review.
Every representative on the application with their identity verification (KYC) status. The top-level kyc_status reflects the primary representative; the application can only be approved once every representative is approved.