Skip to main content
POST
Submit Representative KYC Data

Authorizations

x-api-key
string
header
required

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

Path Parameters

representative_id
string
required
entity_id
string
required

Body

application/json
first_name
string
required

Legal first name.

Minimum string length: 1
Example:

"Felix"

last_name
string
required

Legal last name.

Minimum string length: 1
Example:

"Whiskers"

date_of_birth
string<date>
required

Date of birth (YYYY-MM-DD).

id_number
string<password>
required
write-only

Government ID number. For us_ssn use nine digits, with or without dashes (123-45-6789 or 123456789); for us_ssn_last_4 use the last four digits. Formatting characters are stripped before verification.

Example:

"123-45-6789"

address
OnboardingAddress · object
required

Residential address.

ip
string<ipvanyaddress>
required

IPv4 or IPv6 address of the end user submitting this verification. Forwarded to the identity-verification provider as a fraud signal.

Example:

"203.0.113.42"

id_type
enum<string>
default:us_ssn

Type of government ID (e.g. us_ssn, us_ssn_last_4).

Available options:
ar_dni,
au_drivers_license,
au_passport,
br_cpf,
ca_sin,
cl_run,
cn_resident_card,
co_nit,
dk_cpr,
eg_national_id,
es_dni,
es_nie,
hk_hkid,
in_pan,
in_epic,
it_cf,
jo_civil_id,
jp_my_number,
ke_huduma_namba,
kw_civil_id,
mx_curp,
mx_rfc,
my_nric,
ng_nin,
nz_drivers_license,
om_civil_id,
ph_psn,
pl_pesel,
ro_cnp,
sa_national_id,
se_pin,
sg_nric,
tr_tc_kimlik,
us_ssn,
us_ssn_last_4,
za_smart_id
phone_number
string | null

Phone number in E.164 format (e.g. +14155550123).

Pattern: ^\+[1-9]\d{1,14}$
Example:

"+14155550123"

Response

Successful Response

representative_id
string<uuid>
required

ID of the representative whose KYC was submitted.

kyc_status
enum<string>
required

This representative's identity verification status right after submission. It completes asynchronously; track this representative's status in the representatives array on GET /entities/{entity_id} or via the identity_verification.* webhooks. The entity's top-level kyc_status reflects only the primary representative, and next_step advances once every representative has started verification (not once they pass) — so neither confirms this representative's outcome.

Available options:
not_started,
pending,
action_required,
approved,
rejected