GET
/
accounts
/
{address}
/
kyc
/
{kyc_id}
Get KYC status
curl --request GET \
  --url https://grid.squads.xyz/api/grid/v1/accounts/{address}/kyc/{kyc_id} \
  --header 'Authorization: Bearer <token>'
{
  "data": {
    "id": "123e4567-e89b-12d3-a456-426614174020",
    "account": "9WzDXwBbmkg8ZTbNMqUxvQRAyrZzDsGYdLVL9zYtAWWM",
    "type": "individual",
    "status": "approved",
    "tos_status": "approved",
    "rejection_reasons": [],
    "requirements_due": [],
    "created_at": "2023-07-15T14:30:00.000Z",
    "updated_at": "2023-07-16T10:15:00.000Z"
  },
  "metadata": {
    "request_id": "123e4567-e89b-12d3-a456-426614174022",
    "timestamp": "2023-07-16T10:30:00.000Z"
  }
}
Check the current verification status of a KYC request. Use this endpoint to monitor progress and determine account compliance status.

​
Verification Status Values

The verification process can result in these statuses:
  • not_started: Verification link created but not accessed
  • under_review: Documents submitted and being reviewed
  • incomplete: Additional information required
  • approved: Verification completed successfully
  • rejected: Verification failed

​
Terms of Service Status

Separate from KYC verification, terms of service acceptance is tracked:
  • pending: Terms not yet accepted
  • approved: Terms accepted

​
Important Notes

  • Status updates may take a few minutes to reflect
  • Rejected verifications include detailed rejection reasons
  • Incomplete verifications provide required next steps
  • Some statuses trigger webhooks if configured

Authorizations

​
Authorization
string
header
required

API key authentication with Bearer token. Include the API key in the Authorization header as 'Bearer YOUR_API_KEY'

Path Parameters

​
address
string
required

Account address

Example:

"11111111111111111111111111111112"

​
kyc_id
string<uuid>
required

KYC verification ID

Response

200
application/json

KYC status retrieved successfully

The response is of type object.