Retrieve a stored chat completion
Look up a previously created chat completion by its opaque id (cmp_<ulid>). Returns the reconstructed ChatCompletionResponse with the actuals committed at completion time. Cross-team lookups return 404 (no enumeration leak).
Authorizations
Your team API key (starts with al_live_).
Headers
Optional API version pin (YYYY-MM-DD). Defaults to your team's pinned version, or the system default 2026-05-15 for unauthenticated requests.
^\d{4}-\d{2}-\d{2}$"2026-05-15"
Path Parameters
Opaque chat completion id (cmp_).
"cmp_01HXMQ7Z3K8Y2ABCDEFGHJKM"
Response
Reconstructed chat completion.
Opaque chat-completion id.
"cmp_01HXMQ7Z3K8Y2ABCDEFGHJKM"
chat.completion Unix timestamp (seconds).
1731948000
Aurous model slug used.
"aurous-grow-2.0-pro"
Always exactly 1 entry in v1.0.
Aurous extension: terminal state of the chat completion. completed is the normal happy path. in_progress means the request is still being processed (only possible when polling GET /:id during a streamed request). failed means the provider or platform errored — see error for the typed reason. cancelled means a cancel was requested or the client disconnected.
completed, in_progress, failed, cancelled "completed"
Aurous extension: present only when status is failed or cancelled (in addition to the main error response when applicable). Echoes the typed error envelope shape so customers can branch on error.code without parsing string messages.
{
"code": "chat_provider_unavailable",
"type": "server_error",
"message": "Provider request failed."
}

