Simulate Application Approval
⚠️ Sandbox & development only. Simulation endpoints are not available in production and return
404 Not Foundthere.
Approves a submitted onboarding application in the sandbox as if the compliance review had passed, and kicks off checking-account onboarding for the selected product. Every representative must have passed identity verification (kyc_status is approved) first: like real review, the simulation will not approve an application whose beneficial owner failed KYC, and returns 400 until they pass. Requires an entity API key scoped to the requested entity, or a global API key with the simulations:write scope whose user administers the entity; the application must already be submitted. The application status moves to submitted immediately and to approved once the checking account activates. Poll GET /entities/{entity_id} or subscribe to application.* webhooks to observe the transition. Safe to call repeatedly: if account opening stalls in the sandbox, calling this again completes it.
Authorizations
Your Meow API key, sent in the x-api-key header for authentication.
Path Parameters
Body
The checking account product to open once the application is approved. Defaults to grasshopper.
grasshopper, crb 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.
Link where the primary representative reviews and accepts the required agreements and disclosures in their browser. Populated once the application has been submitted; share it with the primary representative. The link needs no login and anyone holding it can accept on the business's behalf, so treat it as a secret.
Progress through the agreements at consent_url. Populated alongside it once the application has been submitted. Consent is collected in parallel with review, so status moves to under_review on submission whether or not these are accepted. Poll this field, not status, to see whether the primary representative still owes anything.