Resolve a context ref to its id

GET

/api/contexts/resolve

Maintainer:Not configured

OperationId:resolve_context

The caller's own visibility bounds the answer: a context the caller cannot read answers
exactly as one that does not exist (uniform 404, no existence oracle; for a +team ref from a
caller who is not a member of the team, one uniform 403). A +team/slug ref resolves for any
caller who reads that context, member or not. The resolution is
[context_service::resolve_context_ref] — the same one every ref-accepting route uses — so
each ref form keeps the refusal it has everywhere else.

Request

Authorization

JWT Bearer

Add the parameter

Authorization

to Headers

Example:

Authorization: ********************

Query Params

Header Params

Responses

🟢200OK

application/json

The ref resolved to a context the caller can read

Bodyapplication/json

🟠400Bad Request

🟠401Unauthorized

🟠403Forbidden

🟠404Record Not Found

Request Example

Shell

JavaScript

Java

Swift

curl --location '/api/contexts/resolve?context_ref=undefined' \
--header 'X-Temper-Surface;' \
--header 'Authorization: Bearer <token>'

Response Example

200 - Example 1

{
    "context_id": "f31d7249-b7b1-4729-b3a4-ec0ba07b4686"
}

Modified at 2026-11-08 21:00:00

Create a context

Get one context