Users
Re-issue verification
Re-trigger KYC/KYB for a user that came back REJECTED, without re-creating them.
type selects how the user completes verification:
"embedded-link"(this example) — Kira returns a hosted KYC link (verification_linkin the response); your end user opens it and completes verification on Kira’s page. Same flow asverification_mode: "verification_link"on Create User."api"— you submit the corrected KYC data yourself via ametadataobject. Same flow asverification_mode: "automatic"on Create User.
Requires the Idempotency-Key header. Note: this endpoint does not accept verification_mode — that field belongs to Create User (POST /v1/users).
POST
Re-issue verification
Authorizations
Access token from POST /auth (the data.access_token value).
API key issued by Kira. Required on every request, including /auth.
Headers
Example:
"2026-04-14"
Example:
"{{idempotency_key}}"
Path Parameters
User UUID.
Body
application/json
Response
Created.
Previous
List virtual accountsUse `limit<=100` — `GET /v1/virtual-accounts?limit>100` returns a raw `500 "Internal server error"` (same known cap as `GET /v1/users`; applies to ALL list endpoints). Note `provider` and `currency` come back `null` in the list view — fetch by ID if you need them.
Next
Re-issue verification