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.
Example Requests
Using the internal session ID:
cURL
curl -X GET "https://eu.whitecircle.com/api/session/123e4567-e89b-12d3-a456-426614174000" \
-H "Authorization: Bearer wc-your-api-key" \
-H "whitecircle-version: 2026-04-15"Using your external session ID:
cURL
curl -X GET "https://eu.whitecircle.com/api/session?external_session_id=user-session-123" \
-H "Authorization: Bearer wc-your-api-key" \
-H "whitecircle-version: 2026-04-15"Response
The endpoint returns the same session envelope as POST /api/session:
session— The session-level verdict, IDs, and policy statusesartifacts— The artifact result objects for content associated with that session response
Authorizations
Headers
Path Parameters
Query Parameters
Response
Success
sessionobjectrequiredShow child attributesHide child attributes
artifactsobject[]requiredShow child attributesHide child attributes
artifacts.policies objectrequiredartifacts.kind stringrequiredartifacts.status stringrequiredartifacts.internal_artifact_id stringrequiredartifacts.flagged boolean | nullartifacts.updated_at string | nullartifacts.external_artifact_id string | nullartifacts.external_session_id string | nullartifacts.internal_session_id string | nullartifacts.created_at string | nullartifacts.note string | null
Bad Request