# Telegram Phone Number Scraper (`scraperoka/telegram-phone-number-scraper`) Actor 📱 Telegram Phone Number Scraper extracts phone numbers from Telegram publicly available profiles & channels. 🚀 Fast, reliable & efficient for lead generation, B2B outreach, and market research. ✅ Start building targeted lists today! 💼 - **URL**: https://apify.com/scraperoka/telegram-phone-number-scraper.md - **Developed by:** [Scraperoka](https://apify.com/scraperoka) (community) - **Categories:** Lead generation, Social media, Automation - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $1.99 / 1,000 results This Actor is paid per event and usage. You are charged both the fixed price for specific events and for Apify platform usage. 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/docs.md): ```bash npm install apify-client ``` In Python projects, use official [Python client library](https://docs.apify.com/api/client/python/docs.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/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 ### Telegram Phone Number Scraper 🔍 **Telegram Phone Number Scraper** is an Apify actor that **scrapes phone numbers from Telegram profiles, bios, and post content** using your **keywords** and **country targeting**. Whether you’re looking for a **telegram phone number scraper** for outreach, a **telegram phone number finder** for research, or a **telegram leads scraper** for B2B enrichment, this tool helps you automate phone number extraction at scale—saving you hours of manual searching. --- ### Why choose Telegram Phone Number Scraper? | Feature | Benefit | | --- | --- | | ✅ **Keyword-driven scraping** | Uses your keywords to focus results on the people and niches you care about | | ✅ **Country and dial-code targeting** | Filters phone numbers to the country you select for more relevant leads | | ✅ **Bulk extraction with a stop limit** | Stops after reaching your `maxPhoneNumbers` goal to keep runs predictable | | ✅ **Reliability improvements** | Includes resilience behaviors and can resume progress during longer runs | | ✅ **Structured dataset output** | Saves results with clear fields like `phone_number`, `url`, `title`, and `dial_code` | | ✅ **Scales to large tasks** | Designed for large scraping runs—use input keywords and limits to control duration | --- ### Key features - 🔍 **Phone number extraction from public Telegram content**: Pulls phone numbers from Telegram bios, profiles, and post content. - 🎯 **Keyword + country targeting**: Lets you steer results with `keywords`, `country`, and optional `location`. - 🧭 **Progress-aware runs**: Maintains progress so long tasks can continue without restarting from zero. - 🛡️ **Resilient scraping behavior**: Includes retry-and-fallback style handling for more stable collection runs. - 📊 **Clean, table-ready results**: Each match is pushed incrementally into the dataset as a structured record. - 💾 **Deduplication of phone numbers**: Avoids repeating phone numbers within the same run by tracking seen values. - ⏱️ **Run-limiting control**: Use `maxPhoneNumbers` to stop once you reach your target number of unique phone results. - 🤖 **Automation-friendly**: Outputs data you can export to JSON/CSV and feed into CRMs, lists, or analysis pipelines. --- ### Input Provide input via an `input.json` file. Example structure: ```json { "keywords": ["marketing", "founder"], "location": "London", "country": "United Kingdom (+44)", "maxPhoneNumbers": 20 } ```` #### Input Fields | Field | Required | Description | | --- | --- | --- | | `keywords` | ✅ | A list of keywords to search for (for example: `["marketing","founder"]`). These keywords guide which Telegram content is considered for phone number extraction. | | `location` | ❌ | Filter results by location (for example: `"London"` or `"California"`). Leave empty for global targeting. | | `country` | ✅ | Select the country to target for phone numbers. Choose a value like `"United Kingdom (+44)"` to apply the correct country dial-code context. | | `maxPhoneNumbers` | ❌ | Stop scraping after this many phone numbers are found. This helps control run duration. Allowed range is 1–10000; default is `20`. | *** ### Output The actor saves each scraped match into a dataset in **JSON format**. Results are pushed incrementally as records with the following fields. Example output for one record: ```json { "platform": "Telegram", "keyword": "marketing", "title": "No title", "description": "No data", "url": "No URL", "phone_number": "+447700900123", "country": "United Kingdom", "dial_code": "+44" } ``` #### Output Fields | Field | Type | Description | | --- | --- | --- | | `platform` | string | The source platform name used for each record (`Telegram`). | | `keyword` | string | The keyword that was used to guide the scraping for this result. | | `title` | string | The scraped result title (as captured from the source page snippet). | | `description` | string | Text description extracted alongside the result (used as the source where phone numbers are identified). | | `url` | string | The source URL for the record. | | `phone_number` | string | The extracted phone number in E.164 format (e.g. `+44...`). | | `country` | string | The targeted country name (derived from the selected country input). | | `dial_code` | string | The dial code associated with the selected target country. | Notes: the dataset view is titled **“Scraped Phone Numbers”** and the dataset transformation/display corresponds to these fields: `keyword`, `title`, `description`, `url`, `phone_number`, `country`, `dial_code`. *** ### How to use Telegram Phone Number Scraper (via Apify Console) 1. **Open Apify Console**\ Log in at https://console.apify.com and go to the **Actors** tab. 2. **Find the actor**\ Search for **Telegram Phone Number Scraper** and open the actor details page. 3. **Configure the INPUT**\ In the **INPUT** panel, set: - **`keywords`** (required): add the terms you want to use (e.g. marketing, founder) - **`country`** (required): pick the country you want phone numbers from - **`location`** (optional): add a city/region to narrow targeting - **`maxPhoneNumbers`** (optional): set a cap for how many unique phone numbers you want 4. **(Optional) Review Run Options timeout**\ The actor notes that large scraping tasks may take time; you can adjust the timeout in **Run Options** (default is **3600s / 1hr**). 5. **Run the actor**\ Click **Run** to start scraping. During the run, you’ll see logs as the actor discovers and pushes results incrementally to the dataset. 6. **Monitor progress and results**\ If results are fewer than expected, broaden your keywords or use different country settings. 7. **Open the dataset**\ After the run completes, open the dataset named **“Telegram Phone Numbers Dataset”** (view: **“Scraped Phone Numbers”**) and export the data (JSON/CSV as supported by Apify). No coding required—get **telegram phone number extraction tool** results in minutes. *** ### Advanced features & SEO optimization - 🧠 **Engineered for telegram phone number extraction tool workflows**: The actor is built to help you **scrape telegram phone numbers** and export them in a structured, dataset-ready format. - 🎛️ **Smart keyword + country controls**: Using keywords and a selected country improves lead relevance—ideal for a **telegram contact harvesting tool**. - 🔄 **Resumable progress behavior**: Keeps track of progress during long scraping tasks so you can continue rather than restarting. - 📌 **Deduplicated output**: Avoids repeating the same extracted phone number within the run to keep your results clean. - 📊 **Dataset-first output for analysis**: Each result includes `url`, `title`, `description`, `phone_number`, `country`, and `dial_code`, making it easy for analysts and marketers to work with. *** ### Best use cases - 📈 **B2B lead generation**: Build targeted outreach lists using a **telegram leads scraper** approach—keyword + country focused. - 🎓 **Market research**: Collect a **telegram phone number database scraper** dataset to compare phone availability by region and niche. - 🧾 **Compliance-oriented audits of public contact availability**: Validate how often publicly shared phone numbers appear in profiles and bios for a given country. - 🧠 **OSINT research pipelines**: Enrich research notes with **telegram phone number OSINT tool** outputs for further investigation. - 💼 **Recruiting and founder outreach**: Use **telegram user phone number lookup** style harvesting to locate founders and professionals matching your keywords. - 🧰 **CRM ingestion for data analysts**: Feed exported JSON/CSV into downstream pipelines once you have `phone_number`, `url`, and country context. *** ### Technical specifications - **Supported Input Formats** - ✅ `keywords` (array of strings) - ✅ `location` (string; optional) - ✅ `country` (string from the provided enum values like `United Kingdom (+44)`) - ✅ `maxPhoneNumbers` (integer, 1–10000; default `20`) - **Proxy Support** - ✅ Built-in proxy support for reliable scraping in environments where network access may vary. - **Retry Mechanism** - ✅ Includes resilience behaviors and fallback handling for more stable runs. - **Dataset Structure** - ✅ Saves records with: `platform`, `keyword`, `title`, `description`, `url`, `phone_number`, `country`, `dial_code`. - **Limitations** - ⚠️ Results depend on what phone numbers are publicly available in Telegram bios, profiles, and post content for your selected keywords and country. - ⚠️ The run stops when it reaches `maxPhoneNumbers` (and free runs may apply an internal cap). *** ### FAQ #### Can I scrape phone numbers globally instead of by city? ✅ Yes. Leave `location` empty and set only `country`. The actor will target the selected country while keeping the search broad. #### What happens if I get fewer results than expected? ❌ If you receive fewer phone numbers than expected, the actor suggests trying broader keywords or different country settings. You can also increase `maxPhoneNumbers` (within allowed limits) if you want more output. #### Are the extracted phone numbers returned in a specific format? ✅ Yes. The dataset field `phone_number` contains the extracted number formatted in **E.164** style (for example, `+44...`). #### Does the actor deduplicate phone numbers? ✅ Yes. It tracks already seen phone numbers during the run and avoids pushing duplicates to the dataset. #### Can this actor run large batches? ✅ Yes. The actor is intended for large scraping tasks, and it notes that you may need to adjust the timeout in **Run Options** (default: **3600s / 1hr**) for bigger workloads. #### What data fields do I get in the dataset? ✅ Each dataset record includes `platform`, `keyword`, `title`, `description`, `url`, `phone_number`, `country`, and `dial_code`. #### Do I need to write code to use Telegram Phone Number Scraper? ✅ No. You can run it directly from **Apify Console** by providing the input values in the built-in form or via `input.json`. #### Is it safe to use for public Telegram data? ✅ The actor works with **publicly available sources**. You’re responsible for following applicable laws and Telegram/platform policies when using the exported results. *** ### Support & feature requests Want to improve your **Telegram Phone Number Scraper** results? Let us know what’s missing. - 💡 **Feature Requests**: Tell us what you’d like to add next (for example: additional output fields, export enhancements, or stricter filtering for specific use cases). - 📧 **Contact**: Reach out at . - Your feedback helps shape the roadmap for better telegram phone number scraper experiences. *** *If you need a **telegram phone number extraction tool** that’s built for dataset-ready output and keyword + country targeting, **Telegram Phone Number Scraper** is a smart way to scale public phone number research efficiently.* *** ### Disclaimer This tool accesses **publicly accessible sources**. It does not access private profiles, password-protected pages, or authenticated data. You are responsible for complying with applicable laws and regulations (for example, GDPR/CCPA), as well as respecting Telegram and other platform terms of service, and applicable anti-spam rules. If you need help with data removal requests, contact . Please use this actor responsibly, ethically, and for legitimate purposes only. # Actor input Schema ## `keywords` (type: `array`): Enter keywords to search for (e.g., 'Target Keyword'). ## `location` (type: `string`): Filter by location (e.g., 'London', 'California'). Leave empty for global search. ## `country` (type: `string`): Select the country to target for phone numbers. ## `maxPhoneNumbers` (type: `integer`): Stop scraping after this many phone numbers are found. Setting a higher limit extends the scraping duration. ## Actor input object example ```json { "keywords": [ "marketing", "founder" ], "country": "United Kingdom (+44)", "maxPhoneNumbers": 20 } ``` # 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 = { "keywords": [ "marketing", "founder" ] }; // Run the Actor and wait for it to finish const run = await client.actor("scraperoka/telegram-phone-number-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 = { "keywords": [ "marketing", "founder", ] } # Run the Actor and wait for it to finish run = client.actor("scraperoka/telegram-phone-number-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 '{ "keywords": [ "marketing", "founder" ] }' | apify call scraperoka/telegram-phone-number-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=scraperoka/telegram-phone-number-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Telegram Phone Number Scraper", "description": "📱 Telegram Phone Number Scraper extracts phone numbers from Telegram publicly available profiles & channels. 🚀 Fast, reliable & efficient for lead generation, B2B outreach, and market research. ✅ Start building targeted lists today! 💼", "version": "0.1", "x-build-id": "1j7A5yalA4UQhtTap" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/scraperoka~telegram-phone-number-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-scraperoka-telegram-phone-number-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/scraperoka~telegram-phone-number-scraper/runs": { "post": { "operationId": "runs-sync-scraperoka-telegram-phone-number-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/scraperoka~telegram-phone-number-scraper/run-sync": { "post": { "operationId": "run-sync-scraperoka-telegram-phone-number-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", "required": [ "keywords", "country" ], "properties": { "keywords": { "title": "Keywords", "type": "array", "description": "Enter keywords to search for (e.g., 'Target Keyword').", "default": [ "marketing", "founder" ], "items": { "type": "string" } }, "location": { "title": "Location", "type": "string", "description": "Filter by location (e.g., 'London', 'California'). Leave empty for global search." }, "country": { "title": "Country", "enum": [ "Afghanistan (+93)", "Albania (+355)", "Algeria (+213)", "Andorra (+376)", "Angola (+244)", "Antigua And Barbuda (+1-268)", "Argentina (+54)", "Armenia (+374)", "Australia (+61)", "Austria (+43)", "Azerbaijan (+994)", "Bahamas (+1-242)", "Bahrain (+973)", "Bangladesh (+880)", "Barbados (+1-246)", "Belarus (+375)", "Belgium (+32)", "Belize (+501)", "Benin (+229)", "Bhutan (+975)", "Bolivia (+591)", "Bosnia And Herzegovina (+387)", "Botswana (+267)", "Brazil (+55)", "Brunei (+673)", "Bulgaria (+359)", "Burkina Faso (+226)", "Burundi (+257)", "Cambodia (+855)", "Cameroon (+237)", "Canada (+1)", "Cape Verde (+238)", "Central African Republic (+236)", "Chad (+235)", "Chile (+56)", "China (+86)", "Colombia (+57)", "Comoros (+269)", "Congo (Democratic Republic) (+243)", "Congo (Republic) (+242)", "Costa Rica (+506)", "Croatia (+385)", "Cuba (+53)", "Cyprus (+357)", "Czech Republic (+420)", "Denmark (+45)", "Djibouti (+253)", "Dominica (+1-767)", "Dominican Republic (+1-809)", "East Timor (+670)", "Ecuador (+593)", "Egypt (+20)", "El Salvador (+503)", "Equatorial Guinea (+240)", "Eritrea (+291)", "Estonia (+372)", "Eswatini (+268)", "Ethiopia (+251)", "Fiji (+679)", "Finland (+358)", "France (+33)", "Gabon (+241)", "Gambia (+220)", "Georgia (+995)", "Germany (+49)", "Ghana (+233)", "Greece (+30)", "Grenada (+1-473)", "Guatemala (+502)", "Guinea (+224)", "Guinea-Bissau (+245)", "Guyana (+592)", "Haiti (+509)", "Honduras (+504)", "Hungary (+36)", "Iceland (+354)", "India (+91)", "Indonesia (+62)", "Iran (+98)", "Iraq (+964)", "Ireland (+353)", "Israel (+972)", "Italy (+39)", "Jamaica (+1-876)", "Japan (+81)", "Jordan (+962)", "Kazakhstan (+7)", "Kenya (+254)", "Kiribati (+686)", "Korea, North (+850)", "Korea, South (+82)", "Kuwait (+965)", "Kyrgyzstan (+996)", "Laos (+856)", "Latvia (+371)", "Lebanon (+961)", "Lesotho (+266)", "Liberia (+231)", "Libya (+218)", "Liechtenstein (+423)", "Lithuania (+370)", "Luxembourg (+352)", "Madagascar (+261)", "Malawi (+265)", "Malaysia (+60)", "Maldives (+960)", "Mali (+223)", "Malta (+356)", "Marshall Islands (+692)", "Mauritania (+222)", "Mauritius (+230)", "Mexico (+52)", "Micronesia (+691)", "Moldova (+373)", "Monaco (+377)", "Mongolia (+976)", "Montenegro (+382)", "Morocco (+212)", "Mozambique (+258)", "Myanmar (+95)", "Namibia (+264)", "Nauru (+674)", "Nepal (+977)", "Netherlands (+31)", "New Zealand (+64)", "Nicaragua (+505)", "Niger (+227)", "Nigeria (+234)", "North Macedonia (+389)", "Norway (+47)", "Oman (+968)", "Pakistan (+92)", "Palau (+680)", "Panama (+507)", "Papua New Guinea (+675)", "Paraguay (+595)", "Peru (+51)", "Philippines (+63)", "Poland (+48)", "Portugal (+351)", "Qatar (+974)", "Romania (+40)", "Russia (+7)", "Rwanda (+250)", "Saint Kitts And Nevis (+1-869)", "Saint Lucia (+1-758)", "Saint Vincent And The Grenadines (+1-784)", "Samoa (+685)", "San Marino (+378)", "Sao Tome And Principe (+239)", "Saudi Arabia (+966)", "Senegal (+221)", "Serbia (+381)", "Seychelles (+248)", "Sierra Leone (+232)", "Singapore (+65)", "Slovakia (+421)", "Slovenia (+386)", "Solomon Islands (+677)", "Somalia (+252)", "South Africa (+27)", "South Sudan (+211)", "Spain (+34)", "Sri Lanka (+94)", "Sudan (+249)", "Suriname (+597)", "Sweden (+46)", "Switzerland (+41)", "Syria (+963)", "Taiwan (+886)", "Tajikistan (+992)", "Tanzania (+255)", "Thailand (+66)", "Togo (+228)", "Tonga (+676)", "Trinidad And Tobago (+1-868)", "Tunisia (+216)", "Turkey (+90)", "Turkmenistan (+993)", "Tuvalu (+688)", "Uganda (+256)", "Ukraine (+380)", "United Arab Emirates (+971)", "United Kingdom (+44)", "United States (+1)", "Uruguay (+598)", "Uzbekistan (+998)", "Vanuatu (+678)", "Vatican City (+39-06)", "Venezuela (+58)", "Vietnam (+84)", "Yemen (+967)", "Zambia (+260)", "Zimbabwe (+263)" ], "type": "string", "description": "Select the country to target for phone numbers.", "default": "United Kingdom (+44)" }, "maxPhoneNumbers": { "title": "Max Phone Numbers", "minimum": 1, "maximum": 10000, "type": "integer", "description": "Stop scraping after this many phone numbers are found. Setting a higher limit extends the scraping duration.", "default": 20 } } }, "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 } } } } } } } } } } ```