# RequestList Bridge (`pocesar/request-list-bridge`) Actor

Allows you to filter (thus cleaning up your list) and append new data to those requests before
sending to your target task.

Also enables a workaround to provide requestsFromUrl to existing actors that don't support it natively.

- **URL**: https://apify.com/pocesar/request-list-bridge.md
- **Developed by:** [Paulo Cesar](https://apify.com/pocesar) (community)
- **Categories:** Developer tools, Open source
- **Stats:** 10 total users, 1 monthly users, 0.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

Pay per usage

This Actor is paid per platform usage. The Actor is free to use, and you only pay for the Apify platform usage, which gets cheaper the higher subscription plan you have.

Learn more: https://docs.apify.com/actors/running/actors-in-store.md#pay-per-usage

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

## RequestList Bridge

Allows you to filter (thus cleaning up your list) and append new data to those requests before
sending to your target task.

Also enables a workaround to provide `requestsFromUrl` to existing actors that dont't support it natively.

### Example

Target task accepts a `startUrls` but as a plain string array:

```jsonc
{
    "taskId": "x02LumCy0WXdGP7nt",
    "requestListSources": [
        {
            "requestsFromUrl": "https://apify-uploads-prod.s3.amazonaws.com/Hhewqx4YNnyWz2qGk-data.csv"
        }
    ],
    "plainArray": true,
    "targetStartUrlsProperty": "startUrls"
}
```

Target task accepts `RequestQueue` only:

```jsonc
{
    "taskId": "x02LumCy0WXdGP7nt",
    "requestListSources": [
        {
            "requestsFromUrl": "https://apify-uploads-prod.s3.amazonaws.com/Hhewqx4YNnyWz2qGk-data.csv"
        }
    ],
    "targetStartUrlsProperty": "startUrls"
}
```

Filter out and transform the requests:

```js
{
    filter: (req) => /apify/i.test(req.url),
    map: (req) => {
        req.userData.isMapped = true;
        return req;
    },
}
```

### License

Apache 2.0

# Actor input Schema

## `taskId` (type: `string`):

Unique task ID

## `requestListSources` (type: `array`):

The sources to pass to the target actor

## `targetStartUrlsProperty` (type: `string`):

Usually it's startUrls

## `plainArray` (type: `boolean`):

Target startUrls uses plain arrays instead a requestSource list

## `extraInput` (type: `object`):

Provide extra input to be passed to the target

## `actorId` (type: `string`):

For metamorph, need to provide an actor ID

## `useMetamorph` (type: `boolean`):

Use metamorph instead of Apify.callTask

## `map` (type: `string`):

Transform each request before passing to the target task. Useful to add userData or change uniqueKey. This happens after filter.

## `filter` (type: `string`):

Filter each request before passing to the target task. This happens before map.

## `limit` (type: `integer`):

Limit the amount of urls

## Actor input object example

```json
{
  "requestListSources": [
    {
      "url": "http://apify.com/url"
    }
  ],
  "targetStartUrlsProperty": "startUrls",
  "extraInput": {
    "hello": "world"
  },
  "map": "(req) => {\n\treturn req;\n}",
  "filter": "(req) => {\n\treturn true;\n}"
}
```

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "targetStartUrlsProperty": "startUrls",
    "map": (req) => {
    	return req;
    },
    "filter": (req) => {
    	return true;
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("pocesar/request-list-bridge").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "targetStartUrlsProperty": "startUrls",
    "map": """(req) => {
\treturn req;
}""",
    "filter": """(req) => {
\treturn true;
}""",
}

# Run the Actor and wait for it to finish
run = client.actor("pocesar/request-list-bridge").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print(f"💾 Check your data here: https://console.apify.com/storage/datasets/{run.default_dataset_id}")
for item in client.dataset(run.default_dataset_id).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "targetStartUrlsProperty": "startUrls",
  "map": "(req) => {\\n\\treturn req;\\n}",
  "filter": "(req) => {\\n\\treturn true;\\n}"
}' |
apify call pocesar/request-list-bridge --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,pocesar/request-list-bridge"
        }
    }
}

```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/JxHKXnqU40pYAuljQ/builds/Z83DtKgPNNUegTfgO/openapi.json