Skip to main content
GET
cURL
Use this endpoint to retrieve a user’s risk level using either email or id.

How it works

White Circle can assess a user’s Risk Score by correlating their recent sessions with policy violations. To enable this:
  1. Send a Check Session request and include the user’s identifier in metadata.user (either id or email).
  2. The Radar service aggregates the user’s recent history and determines whether their behavior indicates elevated risk.
  3. Query GET /api/radar/risk with the same id or email to fetch the current Risk Score.
Risk scoring is based on recent violations linked to the same user identifier. If we detect serious or repeated violations in the recent window, we return an elevated risk score.

Adding user identity to Check Session

Include metadata.user.id or metadata.user.email in your Check Session payload. This lets Radar associate policy outcomes with a specific user over time.
At least one identifier is required: include metadata.user.id or metadata.user.email. For best results, include both.
Provide richer context in metadata.user (for example, IP, email, or name) to improve correlation and the fidelity of the resulting risk analysis.

Fetching the Risk Score

Use this endpoint to retrieve the current risk level for a user:
  • GET /api/radar/risk?email=user@example.com
  • GET /api/radar/risk?id=user-123
If recent violations exist for the user, Radar returns an elevated risk level; otherwise, it returns a normal risk level.

Authorizations

Authorization
string
header
required

API Key required. Format: Bearer wc-your-api-key

Headers

whitecircle-version
string
required

API Version

Query Parameters

email
string | null

User email address (provide either email or id, not both)

id
string | null

External user ID (provide either email or id, not both)

Response

Success

risk_level
enum<string>
required
Available options:
normal,
elevated,
severe