Skip to main content
POST
Submit Entity Application

Authorizations

x-api-key
string
header
required

Your Meow API key, sent in the x-api-key header for authentication.

Path Parameters

entity_id
string
required

Body

application/json
banking_account_product_type
enum<string>
required

The checking account product to open for this entity once it is approved.

Available options:
grasshopper,
crb
product_features
enum<string>[]

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.

Available options:
stablecoins

Response

Successful Response

entity_id
string<uuid>
required

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.

status
enum<string>
required

Current onboarding status.

Available options:
pending_document_upload,
pending_user_action,
submitted,
under_review,
approved,
rejected
business_name
string | null
required

Legal business name.

created_at
string<date-time>
required

ISO 8601 timestamp of when the entity was created.

updated_at
string<date-time>
required

ISO 8601 timestamp of when onboarding was last updated.

documents
OnboardingDocumentStatus · object[]
required

Documents uploaded during onboarding.

kyc_status
enum<string>
required

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.

Available options:
not_started,
pending,
action_required,
approved,
rejected
onboarding_type
enum<string>
required

How this entity was onboarded (e.g. api, smb, partner).

Available options:
api,
smb,
mcp,
partner
next_step
OnboardingNextStep · object
required

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.

representatives
OnboardingRepresentativeKyc · object[]
required

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.