Use get status to drive loading states in your app, refresh after the user returns from the hosted flow, or periodically poll until verification reaches a final outcome.Documentation Index
Fetch the complete documentation index at: https://docs.starkfi.io/llms.txt
Use this file to discover all available pages before exploring further.
The user must already have a KYC session associated with that email (after Create KYC session). If there is no session yet, you will receive a 404 response.
Endpoint
Paths in this guide use the
/kyc prefix only. If your environment uses an extra prefix (for example /api), prepend it when building the request URL.Request
Query
| Field | Type | Required | Description |
|---|---|---|---|
email | string | Yes | Same email used across prepare, OTP, and session creation. |
Example
Responses
200 — Status retrieved
| Field | Description |
|---|---|
status | Overall KYC status stored for that user |
approved | Whether the user is approved for KYC |
session_id | Current verification session identifier |
session_status | Status reported for the session |
session_url | Hosted flow URL when available |
ip_info | Summarized IP / device context (deduplicated by IP) |
is_blocklisted | Whether blocklist signals were raised in document or liveness checks |
400 — Missing email
status: missing_params — "email is required"
404 — No session or not found
Thestatus and message fields reflect the reason (for example no KYC session exists for that email). The response body may include a details field with more context.
500 — Server error
status: server_failed — "Server failed on KYC status"
.png?fit=max&auto=format&n=I_v6ul4JDafNKFQP&q=85&s=f0ad25536f8a3ca42331fcff88ab2b26)