Get a user

⚠️
Preview — this feature is being built; the design below is the spec.
GET https://app.syntic.ai/v1/compliance/users/{user_id}

Return one person’s compliance identity record.

For how this fits into a full workflow, see Compliance API.

Headers

HeaderRequiredValue
AuthorizationYesBearer <admin key>: an Admin API key (sk_admin_...) that carries the compliance:read scope (plus compliance:write for deletions and holds). Enterprise plans only. See Compliance API.
syntic-betaYes, while in previewcompliance-2026-12-01. Without it the call fails with 400 beta_required. See Versioning.

Path parameters

ParameterTypeDescription
user_idstringStarts with user_.

Response

200 OK, Content-Type: application/json

{
  "id": "user_01J9Y0A2C4E6G8J0L2N4",
  "type": "compliance_user",
  "email": "dana@example.com",
  "name": "Dana Lee",
  "status": "active",
  "role_ids": [
    "role_01JCT6U8W0Y2A4C6E8G0"
  ],
  "products": [
    "chat",
    "code",
    "api"
  ],
  "joined_at": "2026-02-10T14:00:00Z",
  "removed_at": null
}

Examples

curl -sS "https://app.syntic.ai/v1/compliance/users/user_01J9Y0A2C4E6G8J0L2N4" \
  -H "Authorization: Bearer $SYNTIC_ADMIN_KEY" \
  -H "syntic-beta: compliance-2026-12-01"

Errors

Errors use the error envelope and carry a request_id. Codes specific to this operation:

StatustypecodeWhen
400invalid_request_errorbeta_requiredThe syntic-beta header is missing.
404not_found_erroruser_not_foundNo person with this id has been a member.
401authentication_errorinvalid_api_keyThe admin key is missing, unknown, revoked or expired.
403permission_erroradmin_key_requiredAn inference key was used.
403permission_errorscope_missingThe admin key lacks the compliance:read (or, for writes, compliance:write) scope.
429rate_limit_errorrate_limitedToo many requests; wait for Retry-After. See Rate-limit headers.
Was this page helpful?