Skip to main content
POST
Mint a short-lived session bound to one customer you own. Use data.url to open the hosted KYC or KYB page. Use data.token as X-Kyc-Session when your own UI calls the KYC platform. A URL that is only https://kyc.yativo.com/{customer_type}/{customer_id} is rejected with 401. Always mint a session at the moment you send the customer to verification.
Call this from your server with your API key. Never put X-Api-Key / X-Api-Secret in a browser or app. Production keys still need an IP whitelist; the customer’s browser does not.
Each call mints a new token. An older unused token stays valid until it expires, is used to submit KYC, or the customer closes the hosted verification tab. Mint again every time you email, redirect, or show a “Continue verification” button. See KYC / KYB verification for hosted vs API flows, and Bans, blocks and access errors for 401/404 causes.

Authorizations

X-Api-Key
string
header
required

Your API key (yativo_pk_...) from Developers → API Keys. Send together with X-Api-Secret.

X-Api-Secret
string
header
required

Your API secret (yativo_sk_...), shown once when the key is created.

Body

application/json
customer_id
string<uuid>
required

A customer you created with POST /customer. Must belong to the calling account.

Example:

"11111111-2222-4333-8444-555555555555"

customer_type
enum<string>
required

Must match the customer's type.

Available options:
individual,
business
Example:

"individual"

Response

Session minted

status
string
Example:

"success"

status_code
integer
Example:

200

message
string
Example:

"Request successful"

data
object