Skip to main content
GET
cURL
Retrieve the results of a previously submitted content check. You can look up a session either by its internal ID path or by your external ID query. Both lookup styles return the same { session, artifacts } envelope as POST /api/session.

Route Shapes

Use one of these routes: deployment_id remains optional on both routes. If you omit it, White Circle uses the deployment associated with your API key.
GET /api/session?external_session_id=... returns the most recently submitted matching session within the same deployment.

Example Requests

Using the internal session ID:
Using your external session ID:

Response

The endpoint returns the same session envelope as POST /api/session:
  • session — The session-level verdict, IDs, and policy statuses
  • artifacts — The artifact result objects for content associated with that session response
If you provided an external_session_id during the original check, you can use it for stable lookups across systems. If you need an exact immutable lookup target, store the returned internal_session_id.

Authorizations

Authorization
string
header
required

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

Headers

whitecircle-version
string
required

API Version

Path Parameters

internal_session_id
string
required

Find a session by its internal session ID

Query Parameters

deployment_id
string

Optional deployment ID to validate session ownership

Response

Success

session
object
required
Example:
artifacts
object[]
required