---
title: "Get request from default request queue"
method: GET
path: "/v2/actor-runs/{runId}/request-queue/requests/{requestId}"
tags: ["Default request queue"]
---

# Get request from default request queue

`GET /v2/actor-runs/{runId}/request-queue/requests/{requestId}`

Returns a request from the default request queue of the Actor run.

This endpoint is a shortcut for getting the run's `defaultRequestQueueId` and then using the
[Get request](/api/v2/request-queue-request-get) endpoint.

## Path parameters

- `runId` string, required
- `requestId` string, required

## Response `200`

- RequestResponse — Response containing a single request from the request queue.
  - `data` Request, required — A request stored in the request queue, including its metadata and processing state.
    - `uniqueKey` string, required — A unique key used for request de-duplication. Requests with the same unique key are considered identical.
    - `url` string, required — The URL of the request.
    - `method` 'GET' | 'HEAD' | 'POST' | 'PUT' | 'DELETE' | 'CONNECT' | 'OPTIONS' | 'TRACE' | 'PATCH'
    - `retryCount` integer — The number of times this request has been retried.
    - `loadedUrl` string, nullable — The final URL that was loaded, after redirects (if any).
    - `payload` union — The request payload, typically used with POST or PUT requests.
      - string
      - object
    - `headers` object, nullable — HTTP headers sent with the request.
    - `userData` RequestUserData — Custom user data attached to the request. Can contain arbitrary fields.
    - `noRetry` boolean, nullable — Indicates whether the request should not be retried if processing fails.
    - `errorMessages` string[], nullable — Error messages recorded from failed processing attempts.
    - `handledAt` string, date-time, nullable — The timestamp when the request was marked as handled, if applicable.
    - `id` string — A unique identifier assigned to the request.

## Other responses

- `400` — Bad request - invalid input parameters or request body.
- `401` — Unauthorized - authentication required or invalid token.
- `402` — Payment required - the user has exceeded their usage limit, does not have enough credits, or the request lacks authentication and payment credentials.
- `403` — Forbidden - insufficient permissions to perform this action.
- `404` — Not found - the requested resource does not exist.
- `405` — Method not allowed.
- `429` — Too many requests - rate limit exceeded.

## Changes

> 7 revisions in range; 4 could not be searched.

- **2026-07-26** `b94a8abdfff1` — 7 warning
  - added the new `cannot-monetize-without-payout-billing-info` enum value to the `error/type` response property for the response status `400`
  - added the new `cannot-monetize-without-payout-billing-info` enum value to the `error/type` response property for the response status `401`
  - added the new `cannot-monetize-without-payout-billing-info` enum value to the `error/type` response property for the response status `402`
  - added the new `cannot-monetize-without-payout-billing-info` enum value to the `error/type` response property for the response status `403`
  - …3 more

[Change history](https://skmtc.dev/apify/apis/apify-api/changes/v2/actor-runs/:runId/request-queue/requests/:requestId/get.md)

---

[API](https://skmtc.dev/apify/apis/apify-api.md) · [All operations](https://skmtc.dev/apify/apis/apify-api/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/apify/apify-api/revisions/0a98d6a098a4/schema)
