Current actor
Look up one of your requests
One request your credential made in the last 30 days, by the request id its response carried — route, status, duration, trace id and, for a refusal, its error code and message. Requires no permission.
GET
Get one request the calling credential made
The reference panel describes the current v3 operation. The notes below describe its v2 compatibility API. Follow the v3 request schema for current calls: v3 can move identifiers from the body or query into the URL. Keep the v2 method, path, and payload together when using the compatibility API.
v2 compatibility notes
Every Platform API response carries a request id in theX-Request-Id header, and every JSON
answer also carries it in meta.requestId. The OpenAPI documents and the reference page send one
too. This endpoint answers what Forge recorded about a request your credential made, so a
client can check a request’s outcome later or join it to its own traces.
Authorization
GET /api/v2/requests/{requestId} requires no permission. Any Platform API credential can
call it: a platform API key, a Personal key, or an External Application access token. A request is
filed under the credential that made it; every credential of one External Application (its access
tokens and its companion key) shares the app’s requests.
An id another credential’s request carried, an unknown id, a malformed id and a request older than
30 days all receive the same 404 and code resource_missing, so the endpoint never tells you whether
someone else’s request exists. A request that sends any query parameter or a body is refused with
400 and code bad_request.
Response
Forge never records a request’s body, query string, IP address or headers. Records are kept for
30 days. A record is written just after its response, so a lookup made at once may answer
404
until it lands.

