ApifyRequestQueueClient
Index
Methods
__init__
- Initialize a new instance. - Preferably use the - ApifyRequestQueueClient.openclass method to create a new instance.- Parameters- keyword-onlyapi_client: RequestQueueClientAsync
- keyword-onlymetadata: RequestQueueMetadata
- optionalkeyword-onlyaccess: Literal[single, shared] = 'single'
 - Returns None
add_batch_of_requests
- Add a batch of requests to the queue. - Parameters- requests: Sequence[Request]- The requests to add. 
- optionalkeyword-onlyforefront: bool = False- Whether to add the requests to the beginning of the queue. 
 - Returns AddRequestsResponse
drop
- Returns None
fetch_next_request
- Return the next request in the queue to be processed. - Once you successfully finish processing of the request, you need to call - mark_request_as_handledto mark the request as handled in the queue. If there was some error in processing the request, call- reclaim_requestinstead, so that the queue will give the request to some other consumer in another call to the- fetch_next_requestmethod.- Returns Request | None
get_metadata
- Get metadata about the request queue. - Returns ApifyRequestQueueMetadata
get_request
- Get a request by unique key. - Parameters- unique_key: str- Unique key of the request to get. 
 - Returns Request | None
is_empty
- Check if the queue is empty. - Returns bool
mark_request_as_handled
- Mark a request as handled after successful processing. - Handled requests will never again be returned by the - fetch_next_requestmethod.- Parameters- request: Request- The request to mark as handled. 
 - Returns ProcessedRequest | None
open
- Open an Apify request queue client. - This method creates and initializes a new instance of the Apify request queue client. It handles authentication, storage lookup/creation, and metadata retrieval, and sets up internal caching and queue management structures. - Parameters- keyword-onlyid: str | None- The ID of the RQ to open. If provided, searches for existing RQ by ID. Mutually exclusive with name and alias. 
- keyword-onlyname: str | None- The name of the RQ to open (global scope, persists across runs). Mutually exclusive with id and alias. 
- keyword-onlyalias: str | None- The alias of the RQ to open (run scope, creates unnamed storage). Mutually exclusive with id and name. 
- keyword-onlyconfiguration: Configuration- The configuration object containing API credentials and settings. Must include a valid - tokenand- api_base_url. May also contain a- default_request_queue_idfor fallback when neither- id,- name, nor- aliasis provided.
- optionalkeyword-onlyaccess: Literal[single, shared] = 'single'- Controls the implementation of the request queue client based on expected scenario: - 'single' is suitable for single consumer scenarios. It makes less API calls, is cheaper and faster.
- 'shared' is suitable for multiple consumers scenarios at the cost of higher API usage. Detailed constraints for the 'single' access type:
- Only one client is consuming the request queue at the time.
- Multiple producers can put requests to the queue, but their forefront requests are not guaranteed to be handled so quickly as this client does not aggressively fetch the forefront and relies on local head estimation.
- Requests are only added to the queue, never deleted by other clients. (Marking as handled is ok.)
- Other producers can add new requests, but not modify existing ones. (Modifications would not be included in local cache)
 
 - Returns ApifyRequestQueueClient
purge
- Returns None
reclaim_request
- Reclaim a failed request back to the queue. - The request will be returned for processing later again by another call to - fetch_next_request.- Parameters- request: Request- The request to return to the queue. 
- optionalkeyword-onlyforefront: bool = False- Whether to add the request to the head or the end of the queue. 
 - Returns ProcessedRequest | None
Base class for Apify platform implementations of the request queue client.