Requests
GET /v1/requests/{request_id}. Refetch a recorded exchange, including after an idempotency conflict.
GET /v1/requests/req_01JD8XK4M2 HTTP/1.1
Host: REGION.api.lararouter.com
Authorization: Bearer $LARAROUTER_API_KEYEvery HTTP call, and every line inside a batch, is written to an audit record. This endpoint returns
that record, including the stored response body. It is the follow-up after a
409 idempotency_cache_not_requested, and it keeps answering after the result file has aged out.
There is no list route. You refetch by the request ID you already have: X-Lararouter-Request-Id on
an HTTP response, error.original_request_id on an idempotency conflict, or request_id on a batch
result line.
Requires the requests:read scope.
Records are environment- and region-scoped. A sandbox request ID returns 404 against a live key,
and a request ID from another region returns 404 here.
curl https://REGION.api.lararouter.com/v1/requests/req_01JD8XK4M2 \
-H "Authorization: Bearer $LARAROUTER_API_KEY"{
"id": "req_01JD8XK4M2",
"object": "request",
"created": 1754150400,
"status": "succeeded",
"status_code": 200,
"method": "POST",
"path": "/v1/batches",
"model": "llama-3.3-70b",
"batch_id": "batch_5Rj8Lm2Q",
"custom_id": "ticket_4821",
"entity": ["user:usr_8421"],
"tags": ["feature=support-summary"],
"region": "REGION",
"environment": "live",
"replayed": false,
"original_request_id": null,
"usage": {
"prompt_tokens": 284,
"completion_tokens": 96,
"total_tokens": 380,
"cost_usd": 0.00042
},
"response": {
"id": "batch_5Rj8Lm2Q",
"object": "batch",
"status": "validating"
},
"error": null
}Prop
Type
Retention follows the plan: 90 days on Pay-as-you-go, 13 months on Enterprise. A request ID outside
that window returns 404.
See Idempotency for the retry loop that calls this endpoint, and
Batches for the request_id on each result line.