# X (Twitter) Followers & Following Scraper (`b2b_leads/x-followers-and-following-scraper`) Actor Export followers and following of any X (Twitter) account to clean JSON, CSV or Excel. No login or API key needed. Scrape followers lists, verified followers & subscriptions in bulk. Filter by follower count for lead generation, audience & competitor analysis. - **URL**: https://apify.com/b2b\_leads/x-followers-and-following-scraper.md - **Developed by:** [Chidubem Aneke](https://apify.com/b2b_leads) (community) - **Categories:** Social media, Lead generation, MCP servers - **Stats:** 1 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $0.15 / 1,000 results This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event ## What's an Apify Actor? Actors are a software tools running on the Apify platform, for all kinds of web data extraction and automation use cases. 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. In JavaScript/TypeScript projects, use official [JavaScript/TypeScript client](https://docs.apify.com/api/client/js.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python.md): ```bash pip install apify-client ``` In shell scripts, use [Apify CLI](https://docs.apify.com/cli/docs.md): ````bash # MacOS / Linux curl -fsSL https://apify.com/install-cli.sh | bash # Windows irm https://apify.com/install-cli.ps1 | iex ```bash In AI frameworks, you might use the [Apify MCP server](https://docs.apify.com/platform/integrations/mcp.md). If your project is in a different language, use 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 ## X (Twitter) Followers & Following Scraper — Export Any Account's Social Graph **Turn any X (Twitter) account's followers and following into a clean, structured contact list.** Point it at one or more handles, pick the graphs you want — followers, following, verified followers, or subscriptions — and get one flat JSON row per user, ready for your CRM, spreadsheet, database, or AI pipeline. No X API keys. No developer account. No login. Just enter usernames and press **Start**. > ⚡ **Public data, zero setup** • 🎯 **Followers + following in one run** • 🧩 **Flat, predictable JSON** • 💸 **Pay only for what you export** --- ### Why this Actor - **Skip the official X API.** No $100–$5,000/mo tiers, no OAuth apps, no rate-limit math. - **Both directions at once.** Export *who follows an account* and *who that account follows* in a single run — each row is tagged so you can tell them apart instantly. - **Built for scale.** Results stream straight to the dataset as they arrive. Runs comfortably on **256 MB** and can pull the **entire** follower graph of an account when you set the per-account limit to unlimited. - **Never loses a run to one bad input.** A private, suspended, or misspelled account becomes a tidy `unavailable` row — the rest of your run keeps going. - **Automation-native.** Pipe results to Google Sheets, Airtable, a webhook, your database, or an AI agent via the Apify API and MCP. --- ### Use cases & outcomes **🎯 Lead generation & prospecting** Export the followers of a competitor, a niche influencer, or an industry account, filter for users above a follower threshold, and turn a warm audience into a ready-made prospect list. **🔍 Competitor & audience analysis** Pull a competitor's followers *and* the accounts they follow to understand who they target, who amplifies them, and where their audience overlaps with yours. **🧠 Influencer & creator vetting** Check an influencer's verified followers and subscriptions to gauge real reach and audience quality before a partnership. **📊 Community & network mapping** Snapshot a founder's or brand's social graph over time to track growth, churn, and notable new followers. **🤖 AI agents & RAG pipelines** Feed flat, consistently-named JSON straight into an LLM — no brittle parsing, stable field names, canonical `x.com` URLs on every row. --- ### What you can export | Relationship | Turn on with | You get | |---|---|---| | **Followers** *(default)* | `relationships: ["followers"]` | Every account that follows the source account | | **Following** *(default)* | `relationships: ["following"]` | Every account the source account follows | | **Verified followers** | `relationships: ["verified_followers"]` | Only the verified accounts that follow them | | **Subscriptions** | `relationships: ["subscriptions"]` | Paid subscriptions for the source account | Select any combination — each selected relationship is exported for **every** account you provide. --- ### Quick start 1. Open the Actor in Apify Console. 2. Enter one or more **usernames** (without `@`). 3. Pick your **relationships** (defaults to followers + following). 4. Set **Max users per account** — `100` to sample, or `0` to export the entire graph. 5. Press **Start** and watch rows stream into the dataset. 6. Export as **JSON / CSV / Excel**, or pull via the **Apify API**, **integrations**, or **MCP**. #### Example — followers + following of one account ```json { "usernames": ["nasa"], "relationships": ["followers", "following"], "maxUsersPerAccount": 500 } ```` #### Example — a lead list of large followers ```json { "usernames": ["openai"], "relationships": ["followers"], "minFollowers": 1000, "maxItems": 5000 } ``` #### Example — export the entire following of several accounts ```json { "usernames": ["nasa", "spacex", "esa"], "relationships": ["following"], "maxUsersPerAccount": 0 } ``` #### Example — verified followers only, by user ID ```json { "userIds": ["11348282"], "relationships": ["verified_followers"], "maxUsersPerAccount": 0 } ``` *** ### Input reference | Field | Type | Default | Description | |---|---|---|---| | `usernames` | string\[] | `[]` | X handles to export, without `@`. | | `userIds` | string\[] | `[]` | Numeric user IDs (skips username resolution). | | `relationships` | string\[] | `["followers","following"]` | Any of `followers`, `following`, `verified_followers`, `subscriptions`. Each is exported for every account. | | `maxUsersPerAccount` | integer | `100` | Max users per account **per relationship**. `0` = unlimited (bounded by `maxItems`). | | `minFollowers` | integer | `0` | Keep only exported users with at least this many followers. `0` = off. | | `maxItems` | integer | `100000` | Global ceiling on total exported users — the main cost lever. | | `pageSize` | integer | `1000` | Users requested per page. Does **not** cap totals — the Actor keeps paginating. Higher = fewer requests. | | `maxRetries` | integer | `5` | Automatic retries on rate limits / temporary errors. | | `retryBaseDelayMs` | integer | `2000` | Initial retry backoff (grows exponentially). | | `retryMaxDelayMs` | integer | `30000` | Maximum retry backoff. | | `includeRaw` | boolean | `false` | Attach the untouched source payload under `raw`. | Provide at least one `username` or `userId`. *** ### Output Every exported user is a **flat JSON object**. Rows from different graphs live in the same dataset and are distinguished by `relationshipType` and the `source*` fields. | Field | Type | Description | |---|---|---| | `featureType` / `relationshipType` | string | Which graph this row came from: `followers`, `following`, `verified_followers`, or `subscriptions`. | | `sourceUsername` | string | null | The account whose graph this user belongs to (null when the account was given by ID). | | `sourceUserId` | string | The numeric ID of the source account. | | `inputRef` | string | The username or ID you provided. | | `scrapedAt` | string | ISO 8601 UTC timestamp of collection. | | `id` | string | null | The exported user's numeric ID. | | `username` | string | null | The exported user's handle. | | `displayName` | string | null | Display name. | | `bio` | string | null | Profile bio. | | `url` | string | null | Canonical `https://x.com/...` profile URL. | | `followersCount` | number | null | Follower count. | | `followingCount` | number | null | Following count. | | `tweetCount` | number | null | Total posts. | | `listedCount` / `mediaCount` | number | null | Lists containing the user / media posts. | | `verified` | boolean | null | Legacy verified flag. | | `isBlueVerified` | boolean | null | X Premium (Blue) verification. | | `verifiedType` | string | null | Verification type when present. | | `isProtected` | boolean | null | Whether the account is protected. | | `location` | string | null | Profile location. | | `website` | string | null | Profile website. | | `createdAt` | string | null | Account creation date. | | `profileImageUrl` / `profileBannerUrl` | string | null | Avatar / banner image URLs. | **Example — a follower row:** ```json { "featureType": "followers", "relationshipType": "followers", "scrapedAt": "2026-07-06T12:00:00.000Z", "sourceUrl": "https://x.com/jane_doe", "inputRef": "nasa", "sourceUserId": "11348282", "sourceUsername": "nasa", "id": "6000000000000000001", "username": "jane_doe", "displayName": "Jane Doe", "bio": "Space nerd. Coffee. Code.", "url": "https://x.com/jane_doe", "followersCount": 1200, "followingCount": 340, "tweetCount": 5820, "verified": false, "isBlueVerified": true, "location": "Austin, TX", "profileImageUrl": "https://pbs.twimg.com/profile_images/…" } ``` Couldn't be fetched? You get an explicit marker instead of a silent gap: ```json { "featureType": "unavailable", "status": "unavailable", "reason": "not_found", "message": "User @example not found.", "inputRef": "example", "relationshipType": null, "scrapedAt": "2026-07-06T12:00:00.000Z" } ``` After every run, the **OUTPUT** tab shows a summary: the relationships exported, accounts requested/resolved, counts per relationship, unavailable count, and any non-fatal errors. *** ### Dataset views The dataset ships with ready-made tabbed views in the Console — **Overview, Followers, Following,** and **Unavailable** — so you can read results without building a single filter. Filter on `relationshipType` to split "followers of @X" from "accounts @X follows", even when both are in the same dataset. *** ### Controlling scope & cost | Field | Effect | |---|---| | `maxUsersPerAccount` | The per-account throttle. `100` samples; `0` exports the full graph. | | `maxItems` | The global ceiling and main cost lever. Lower it to keep runs lean. | | `minFollowers` | Trims small accounts out of the results before they're stored. | Large accounts have millions of followers — exporting the full graph uses more compute and time. Start with a modest `maxUsersPerAccount` and raise it once you've confirmed the output looks right. *** ### FAQ **Do I need an X/Twitter API key or login?** No. This Actor exports **public** follower/following data with zero credentials. **Can I export followers *and* following in one run?** Yes — select both in `relationships`. Each row is tagged with `relationshipType` so you can tell them apart. **Can I get *all* followers of an account?** Yes — set `maxUsersPerAccount` to `0` (unlimited). The run is then bounded only by `maxItems`. **What formats can I export?** JSON, CSV, Excel, HTML, or RSS — plus the Apify API, webhooks, and integrations. **Will one bad username break my run?** No. Failed accounts become `unavailable` rows and the run continues. **Can I schedule it?** Yes — use Apify Schedules to run on any cron you like. *** ### Support Open an issue on the Actor page or contact the publisher with your run ID and your (redacted) input JSON. *** ### Contact me Need something built beyond this Actor? I take on **custom projects** — from Apify scrapers and data pipelines to full-stack web apps. | | | |---|---| | **Email** | | | **GitHub** | [github.com/DrunkCodes](https://github.com/DrunkCodes) | Reach out with a short description of your project and timeline — happy to discuss scope and pricing. # Actor input Schema ## `usernames` (type: `array`): X (Twitter) handles to export, without the @ (e.g. nasa, openai). Their followers and/or following will be scraped based on the relationships you select. ## `userIds` (type: `array`): Numeric X user IDs to export. Use this to skip username resolution when you already know the account IDs. ## `relationships` (type: `array`): Which social graphs to export for each account. 'followers' = accounts that follow them; 'following' = accounts they follow; 'verified\_followers' = only verified followers; 'subscriptions' = paid subscriptions. Each selected relationship is exported for every account. ## `maxUsersPerAccount` (type: `integer`): Maximum users to export for each account, for each selected relationship. Set 0 for unlimited (export the entire graph, bounded only by Max items). Example: 100 with followers+following returns up to 100 followers AND up to 100 following per account. ## `minFollowers` (type: `integer`): Only keep exported users who have at least this many followers. Useful for building lead lists of larger accounts. 0 = no filter. ## `maxItems` (type: `integer`): Hard ceiling on the total number of users exported in this run, across all accounts and relationships. This is the main cost lever. Lower it to keep runs small. ## `pageSize` (type: `integer`): How many users to request per page. This does NOT limit your total results — the Actor keeps paginating until it hits Max users per account or Max items. Higher values mean fewer requests. Default 1000. ## `maxRetries` (type: `integer`): How many times to automatically retry a request when the data source is rate-limited or returns a temporary server error. ## `retryBaseDelayMs` (type: `integer`): Initial wait before the first retry. Grows exponentially on each subsequent retry. ## `retryMaxDelayMs` (type: `integer`): Maximum wait between retries, regardless of exponential growth. ## `includeRaw` (type: `boolean`): Attach the untouched source payload for each user under a 'raw' field. For power users who want every available attribute. ## Actor input object example ```json { "usernames": [ "nasa" ], "userIds": [], "relationships": [ "followers", "following" ], "maxUsersPerAccount": 100, "minFollowers": 0, "maxItems": 100000, "pageSize": 1000, "maxRetries": 5, "retryBaseDelayMs": 2000, "retryMaxDelayMs": 30000, "includeRaw": false } ``` # Actor output Schema ## `results` (type: `string`): All exported users, each tagged with relationshipType and the source account they belong to. ## `runSummary` (type: `string`): Per-run metadata: relationships, accounts requested/resolved, counts per relationship, unavailable count, upstream request count, and any non-fatal errors. # 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 '' with your token const client = new ApifyClient({ token: '', }); // Prepare Actor input const input = { "usernames": [ "nasa" ], "relationships": [ "followers", "following" ], "maxUsersPerAccount": 100, "pageSize": 1000 }; // Run the Actor and wait for it to finish const run = await client.actor("b2b_leads/x-followers-and-following-scraper").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 '' with your token. client = ApifyClient("") # Prepare the Actor input run_input = { "usernames": ["nasa"], "relationships": [ "followers", "following", ], "maxUsersPerAccount": 100, "pageSize": 1000, } # Run the Actor and wait for it to finish run = client.actor("b2b_leads/x-followers-and-following-scraper").call(run_input=run_input) # Fetch and print Actor results from the run's dataset (if there are any) print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"]) for item in client.dataset(run["defaultDatasetId"]).iterate_items(): print(item) # 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start ``` ## CLI example ```bash echo '{ "usernames": [ "nasa" ], "relationships": [ "followers", "following" ], "maxUsersPerAccount": 100, "pageSize": 1000 }' | apify call b2b_leads/x-followers-and-following-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=b2b_leads/x-followers-and-following-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "X (Twitter) Followers & Following Scraper", "description": "Export followers and following of any X (Twitter) account to clean JSON, CSV or Excel. No login or API key needed. Scrape followers lists, verified followers & subscriptions in bulk. Filter by follower count for lead generation, audience & competitor analysis.", "version": "0.0", "x-build-id": "sjU8I5newj5h1AP9D" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/b2b_leads~x-followers-and-following-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-b2b_leads-x-followers-and-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for its completion, and returns Actor's dataset items in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } }, "/acts/b2b_leads~x-followers-and-following-scraper/runs": { "post": { "operationId": "runs-sync-b2b_leads-x-followers-and-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor and returns information about the initiated run in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK", "content": { "application/json": { "schema": { "$ref": "#/components/schemas/runsResponseSchema" } } } } } } }, "/acts/b2b_leads~x-followers-and-following-scraper/run-sync": { "post": { "operationId": "run-sync-b2b_leads-x-followers-and-following-scraper", "x-openai-isConsequential": false, "summary": "Executes an Actor, waits for completion, and returns the OUTPUT from Key-value store in response.", "tags": [ "Run Actor" ], "requestBody": { "required": true, "content": { "application/json": { "schema": { "$ref": "#/components/schemas/inputSchema" } } } }, "parameters": [ { "name": "token", "in": "query", "required": true, "schema": { "type": "string" }, "description": "Enter your Apify token here" } ], "responses": { "200": { "description": "OK" } } } } }, "components": { "schemas": { "inputSchema": { "type": "object", "properties": { "usernames": { "title": "Usernames", "type": "array", "description": "X (Twitter) handles to export, without the @ (e.g. nasa, openai). Their followers and/or following will be scraped based on the relationships you select.", "default": [], "items": { "type": "string" } }, "userIds": { "title": "User IDs (optional)", "type": "array", "description": "Numeric X user IDs to export. Use this to skip username resolution when you already know the account IDs.", "default": [], "items": { "type": "string" } }, "relationships": { "title": "Relationships to export", "type": "array", "description": "Which social graphs to export for each account. 'followers' = accounts that follow them; 'following' = accounts they follow; 'verified_followers' = only verified followers; 'subscriptions' = paid subscriptions. Each selected relationship is exported for every account.", "items": { "type": "string", "enum": [ "followers", "following", "verified_followers", "subscriptions" ], "enumTitles": [ "Followers", "Following", "Verified followers", "Subscriptions" ] }, "default": [ "followers", "following" ] }, "maxUsersPerAccount": { "title": "Max users per account (per relationship)", "minimum": 0, "type": "integer", "description": "Maximum users to export for each account, for each selected relationship. Set 0 for unlimited (export the entire graph, bounded only by Max items). Example: 100 with followers+following returns up to 100 followers AND up to 100 following per account.", "default": 100 }, "minFollowers": { "title": "Minimum followers filter", "minimum": 0, "type": "integer", "description": "Only keep exported users who have at least this many followers. Useful for building lead lists of larger accounts. 0 = no filter.", "default": 0 }, "maxItems": { "title": "Max items (global)", "minimum": 1, "type": "integer", "description": "Hard ceiling on the total number of users exported in this run, across all accounts and relationships. This is the main cost lever. Lower it to keep runs small.", "default": 100000 }, "pageSize": { "title": "Page size (per request)", "minimum": 1, "type": "integer", "description": "How many users to request per page. This does NOT limit your total results — the Actor keeps paginating until it hits Max users per account or Max items. Higher values mean fewer requests. Default 1000.", "default": 1000 }, "maxRetries": { "title": "Max retries", "minimum": 0, "type": "integer", "description": "How many times to automatically retry a request when the data source is rate-limited or returns a temporary server error.", "default": 5 }, "retryBaseDelayMs": { "title": "Retry base delay (ms)", "minimum": 100, "type": "integer", "description": "Initial wait before the first retry. Grows exponentially on each subsequent retry.", "default": 2000 }, "retryMaxDelayMs": { "title": "Retry max delay (ms)", "minimum": 1000, "type": "integer", "description": "Maximum wait between retries, regardless of exponential growth.", "default": 30000 }, "includeRaw": { "title": "Include raw payload", "type": "boolean", "description": "Attach the untouched source payload for each user under a 'raw' field. For power users who want every available attribute.", "default": false } } }, "runsResponseSchema": { "type": "object", "properties": { "data": { "type": "object", "properties": { "id": { "type": "string" }, "actId": { "type": "string" }, "userId": { "type": "string" }, "startedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "finishedAt": { "type": "string", "format": "date-time", "example": "2025-01-08T00:00:00.000Z" }, "status": { "type": "string", "example": "READY" }, "meta": { "type": "object", "properties": { "origin": { "type": "string", "example": "API" }, "userAgent": { "type": "string" } } }, "stats": { "type": "object", "properties": { "inputBodyLen": { "type": "integer", "example": 2000 }, "rebootCount": { "type": "integer", "example": 0 }, "restartCount": { "type": "integer", "example": 0 }, "resurrectCount": { "type": "integer", "example": 0 }, "computeUnits": { "type": "integer", "example": 0 } } }, "options": { "type": "object", "properties": { "build": { "type": "string", "example": "latest" }, "timeoutSecs": { "type": "integer", "example": 300 }, "memoryMbytes": { "type": "integer", "example": 1024 }, "diskMbytes": { "type": "integer", "example": 2048 } } }, "buildId": { "type": "string" }, "defaultKeyValueStoreId": { "type": "string" }, "defaultDatasetId": { "type": "string" }, "defaultRequestQueueId": { "type": "string" }, "buildNumber": { "type": "string", "example": "1.0.0" }, "containerUrl": { "type": "string" }, "usage": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "integer", "example": 1 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } }, "usageTotalUsd": { "type": "number", "example": 0.00005 }, "usageUsd": { "type": "object", "properties": { "ACTOR_COMPUTE_UNITS": { "type": "integer", "example": 0 }, "DATASET_READS": { "type": "integer", "example": 0 }, "DATASET_WRITES": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_READS": { "type": "integer", "example": 0 }, "KEY_VALUE_STORE_WRITES": { "type": "number", "example": 0.00005 }, "KEY_VALUE_STORE_LISTS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_READS": { "type": "integer", "example": 0 }, "REQUEST_QUEUE_WRITES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_INTERNAL_GBYTES": { "type": "integer", "example": 0 }, "DATA_TRANSFER_EXTERNAL_GBYTES": { "type": "integer", "example": 0 }, "PROXY_RESIDENTIAL_TRANSFER_GBYTES": { "type": "integer", "example": 0 }, "PROXY_SERPS": { "type": "integer", "example": 0 } } } } } } } } } } ```