Submit Entity Application
Submit a fully prepared business entity for review. Choose the checking account product to open. The application must have everything it needs first (check next_step.can_submit on the onboarding status); otherwise this returns the outstanding requirements. Once submitted, the application moves to review and can no longer be edited. Pass product_features to request additional products alongside the checking account (for example stablecoins for USDC access); they are enabled once the application is approved. Returns the updated onboarding status, including a consent_url: share it with the primary representative so they can review and accept the required agreements, disclosures, and attestations in their browser (no login needed). The same link is also returned on GET /entities/{entity_id} after submission.
Authorizations
Your Meow API key, sent in the x-api-key header for authentication.
Path Parameters
Body
The checking account product to open for this entity once it is approved.
grasshopper, crb Additional products to request for this entity alongside the checking account. stablecoins requests USDC stablecoin access. The primary representative accepts each requested product's terms on the consent_url page; the product is enabled once they have accepted and the application is approved.
stablecoins 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.