Create a user
Creates a business under your account and starts its verification.
Two ways to verify, set with verification_mode:
automatic— the default. Verification runs now and you receiveuser.*webhooks (see Webhooks).verification_link— Kira drops every other field you sent and answers with a hosted form for someone to fill in.
Authorizations
The data.access_token value from Get access token.
Headers
Version applied to this request. It wins over your account's pinned version — see Versioning.
"2026-06-01"
A UUID you generate for this request. Send a fresh one per business you create.
Reusing a key with the same body returns the original result instead of creating a second business. Reusing it with a different body answers 409.
"3fa85f64-5717-4562-b3fc-2c963f66afa6"
Body
How this business gets verified.
See User values for what each value means.
automatic, verification_link The locale for the hosted verification form. It only matters when verification_mode is verification_link.
See User values for the accepted values.
en, es The legal structure of the business.
See User values for the accepted values.
Accepted here, but not returned in the user object.
The industry the business works in, as a NAICS subsector slug — telecommunications, real_estate, construction_of_buildings.
See User values for the full list. Send one industry. A second is refused with a 400.
Accepted here, but not returned in the user object.
1How much the business expects to receive in payments in a month, as a bucket.
See User values for the buckets.
less_than_50000, 50000_to_100000, 100000_to_500000, 500000_to_1000000, 1000000_to_5000000, 5000000_to_10000000, more_than_10000000 How much the business expects to move in a month.
See User values for the buckets.
less_than_50000, 50000_to_100000, 100000_to_500000, 500000_to_1000000, 1000000_to_5000000, 5000000_to_10000000, more_than_10000000 How many payments the business expects to make in a month.
See User values for the buckets.
less_than_10, 10_to_25, 26_to_50, 51_to_100, 101_to_500, more_than_500 What the business will use the account for.
See User values for the accepted values.
Accepted here, but not returned in the user object.
charitable_donations, ecommerce_retail_payments, investment_purposes, purchase_goods_and_services, receive_payments_for_goods_and_services, internal_treasury, third_party_money_transmission, operating_a_company Where the money the business moves comes from.
See User values for the accepted values.
Accepted here, but not returned in the user object.
business_loans, inter_company_funds, investment_proceeds, owners_capital, sales_of_goods_and_services, tax_refund, third_party_funds, treasury_reserves, company_funds, investments_loans The people behind the business — owners, people in control, and authorized signers. Kira matches them by email.
A business needs at least one beneficial owner. That is a person with has_ownership: true and an ownership_percentage at or above the threshold of the bank that verifies the business: 25 when the business requests jp_morgan, 10 otherwise. Without that, verification does not start and associated_persons:beneficial_owner shows up in missing_fields. A business that is already verified is not re-blocked by this.
A business needs one person who signs. That is a person with is_signer: true. They represent the business in verification. Without one, associated_persons:signer shows up in missing_fields. A business verified through a link declares its representative there instead. A business that is already verified is not re-blocked by this.
The representative_* fields are stored as data. They never add a person to the business.
An owner below that threshold who neither signs nor controls the business is not sent for verification, and nothing is asked of them.
The three roles are independent, and one person can hold all of them.
Your key-value pairs. ≤ 50 keys; key 1–40 chars with no [ or ]; value ≤ 500 chars. Kira can additionally configure client-level default metadata for your account; defaults are merged in at create time (your keys win on conflict), so the stored and returned metadata may include keys you did not send.
Response
The business was created. Verification has not necessarily started — read verification_triggered and missing_fields.