Skip to main content
GET
cURL
Retrieve the results of a previously evaluated Event. You can look up an Event by the internal_event_id returned from POST /api/event or by your own run_id and event_id.

Lookup Methods

Use one of these routes:
For exact lookups, prefer internal_event_id. If you submit the same run_id and event_id more than once, lookup by run_id and event_id returns the latest matching result.

Example Requests

Using the internal Event ID:
Using your Event IDs:
You can also require a specific Event type:

Query Parameters

Pass environment_id on every request to either route. For GET /api/event?run_id=...&event_id=...: If type is provided and the latest matching result has a different Event type, White Circle returns 404.

Response Overview

Lookup Behavior

internal_event_id identifies a single saved result. run_id + event_id returns the latest matching result in the selected environment. This is useful when you use your own Event IDs and only need the newest result. Metrics run asynchronously and are not returned in the synchronous policies map.
If no matching Event is found, or the Event belongs to another team or environment, White Circle returns 404.

Authorizations

Authorization
string
header
required

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

Headers

whitecircle-version
string
required

API Version

Path Parameters

internal_event_id
string
required

Query Parameters

environment_id
string
required

Required environment selector.

Response

Success

event
object
required
flagged
boolean
required
policies
object
required
note
string | null
metadata
any