# Hospital Procurement Email Scraper (`contacts-api/hospital-procurement-email-scraper`) Actor Hospital procurement email scraper to extract verified procurement, purchasing, and supply chain contact emails from hospitals, healthcare systems, and medical organizations πŸ“§πŸ₯ Perfect for vendor outreach, healthcare sales, and medical procurement lead generation. - **URL**: https://apify.com/contacts-api/hospital-procurement-email-scraper.md - **Developed by:** [Lead Heaven](https://apify.com/contacts-api) (community) - **Categories:** Lead generation, Automation, Developer tools - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, NaN bookmarks - **User rating**: No ratings yet ## Pricing from $1.99 / 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 ### πŸ₯ Hospital Procurement Email Scraper β€” Find Verified Contacts In Minutes > The fastest way to build a targeted hospital procurement list. This tool searches Google Maps for hospital procurement departments and related purchasing units across any region, crawls their websites, and extracts verified hospital procurement email addresses, phone numbers, and social links β€” all in one clean, export-ready dataset. --- #### πŸš€ Quick Start 1. Enter your search term β€” e.g., "Hospital Procurement", "Hospital Purchasing", "Healthcare Supply Chain" 2. Add one or more target locations β€” e.g., "New York", "Chicago, Illinois" 3. Set your desired number of businesses with emails 4. Hit Run and get your results in minutes No coding required. Export to CSV, JSON, or Excel instantly. --- #### πŸ’‘ What Is the Hospital Procurement Email Scraper? The Hospital Procurement Email Scraper is a purpose-built lead generation and contact discovery tool for: - Medtech and healthcare suppliers - Group purchasing and distribution teams - B2B sales development reps and SDR managers - Market researchers and analysts It combines Google Maps listing discovery with deep website crawling to extract publicly available contact data β€” producing accurate, deduplicated hospital procurement email records ready for immediate use. Whether you need it as a hospital procurement lead finder, a hospital procurement lead scraper, a hospital procurement email finder, or a hospital procurement email extractor β€” this actor covers them all in a single automated run. It also doubles as a hospital procurement contact scraper and hospital procurement contact finder for teams that need broader contact coverage, and serves as a reliable hospital procurement data scraper for structured exports and BI pipelines. --- #### πŸ“¦ What Data Does It Extract? | Field | Description | |---|---| | Business Name | Hospital or health system name from Google Maps | | Website | Official website URL for the hospital or procurement unit | | Phone | Primary phone from the listing or website | | Full Address | Complete address as listed | | City / State / ZIP | Parsed location components | | Country Code | ISO country code where available | | Emails | All public-facing hospital procurement email addresses discovered on the domain | | Additional Phones | Extra phone numbers discovered during crawl | | Social Media Links | Facebook, LinkedIn, Twitter/X, Instagram, and more | | Email Count | Total unique emails found per hospital | | Pages Scraped | Number of website pages crawled per domain | | Rating | Average Google Maps star rating (if available) | | Reviews | Total number of Google reviews (if available) | | Latitude / Longitude | Geo-coordinates for mapping and filtering | | Place ID | Google Maps place identifier | | Scrape Status | Per-record status: success, partial, or error | All results are normalized to power your hospital procurement leads workflows out of the box. --- #### βš™οΈ Input Configuration ##### Minimal Example ```json { "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": ["New York"], "maxBusinesses": 50 } ```` ##### Full Example with All Options ```json { "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": [ "New York", "Chicago, Illinois", "Los Angeles, California" ], "maxBusinesses": 200, "scrapeMaxBusinessesPerLocation": true, "proxyConfiguration": { "useApifyProxy": true } } ``` ##### Input Parameters | Parameter | Type | Required | Description | |---|---|---|---| | googleMapsSearchTerm | String | βœ… Yes | Business type to search β€” e.g., "Hospital Procurement", "healthcare supply chain", "hospital purchasing" | | googleMapsLocation | Array | βœ… Yes | One or more locations β€” e.g., \["New York", "Austin, Texas"] | | maxBusinesses | Number | βœ… Yes | Max hospitals with emails to return (1–1,000). The run stops at this target. | | scrapeMaxBusinessesPerLocation | Boolean | ❌ No | If true, applies the cap per location. If false, it's a combined total across locations. | | proxyConfiguration | Object | ❌ No | Proxy settings. Strongly recommended for large runs and multi-city campaigns. | *** #### πŸ“€ Sample Output ```json [ { "name": "Riverview Medical Center", "website": "https://www.riverviewmed.org", "phone": "+1 212-555-0142", "full_address": "200 Riverside Dr, New York, NY 10025, United States", "city": "New York", "state": "NY", "zip": "10025", "country_code": "US", "scraped_emails": [ "procurement@riverviewmed.org", "purchasing@riverviewmed.org" ], "scraped_phones": ["+1 212-555-0142", "+1 212-555-0197"], "scraped_social_media": [ "linkedin:https://www.linkedin.com/company/riverview-medical-center", "twitter:https://twitter.com/riverviewmed" ], "emails_found": 2, "pages_scraped": 18, "avg_rating": 4.3, "total_reviews": 862, "lat": 40.7927, "long": -73.9772, "place_id": "ChIJx-EXAMPLERIVER", "scrape_status": "success" } ] ``` *** #### πŸ”§ How It Works β€” Under the Hood ``` Step 1 β†’ Search Google Maps using your term + location Step 2 β†’ Collect hospital listings (name, address, phone, website) Step 3 β†’ Visit each website and crawl key pages (Home, Contact, Supply Chain, Purchasing, RFQ, Vendors) Step 4 β†’ Extract public emails, phone numbers, and social links for procurement/purchasing teams Step 5 β†’ Deduplicate and normalize contact data for export Step 6 β†’ Return structured results ready for CRM, outreach, or analysis ``` This workflow functions as a reliable hospital procurement email extractor and hospital procurement data scraper in one pipeline β€” ideal for teams that need repeatable, at-scale contact discovery. *** #### ✨ Key Features ##### 🎯 Precise Location Targeting Enter any city, state, or region. The actor pinpoints purchasing and supply chain units at hospitals in your exact target areas β€” delivering hyper-local hospital procurement leads. ##### πŸ” Deep Website Crawl Goes beyond the listing. Crawls homepages, vendor instructions, RFQ pages, and contact directories to surface every available hospital procurement email and phone number. Perfect when you need a hospital procurement email finder that actually goes deep. ##### 🧠 Role- and Page-Aware Extraction Looks for procurement, purchasing, sourcing, supply chain, materials management, and vendor relations pages and signals β€” improving precision compared to generic scrapers. ##### 🧹 Smart De-Duplication Automatically removes duplicate emails per domain so your hospital procurement list stays clean and accurate β€” no messy cleanup after export. ##### πŸ“Š Structured, CRM-Ready Output Normalized fields designed for immediate import into HubSpot, Salesforce, Apollo, or your data warehouse β€” ideal for a hospital procurement lead scraper stack. ##### 🌎 Multi-Location Scaling Run across dozens of cities at once with combined or per-location caps β€” great for national hospital procurement leads campaigns. ##### πŸ›‘οΈ Proxy-Ready For Reliability Built-in proxy support enables stable, large-scale runs without rate limits β€” a must for any production-grade hospital procurement contact scraper. ##### ⏱️ Stop Exactly At Your Target The actor halts as soon as your maxBusinesses limit is reached β€” no wasted compute in your hospital procurement email scraper workflow. ##### πŸ”„ Schedulable & Repeatable Run it daily, weekly, or monthly to continuously grow and refresh your pipeline with verified contacts. *** #### 🎯 Use Cases ##### πŸ’Ό B2B Outreach & Sales Build targeted pitch lists for hospital purchasing and supply chain teams. Use it as your hospital procurement lead finder to fuel cold email and SDR sequences with fresh hospital procurement leads. ##### 🧾 Vendor Enrollment & RFQ Prospecting Identify hospitals with open vendor registration or RFQ pages. A practical hospital procurement contact finder for vendor programs and bid alerts. ##### πŸ§ͺ Medtech & Device Launches Quickly assemble regional targets for product demos and evaluations, powered by a repeatable hospital procurement data scraper. ##### πŸ“£ Channel & Partner Enablement Share clean exports with distributors and channel partners, keeping everyone aligned on the same hospital procurement list. ##### πŸ“š Market Research & Mapping Enrich your market maps with procurement contacts, phone numbers, and social profiles β€” a lightweight hospital procurement lead scraper when you need quick coverage. *** #### πŸ“ˆ How Many Results Can You Get? Scale from a small prospect list to a robust regional database β€” results depend on: - Number of locations added - Search term breadth (niche vs. broad) - Website density and email visibility in each market - maxBusinesses setting and per-location vs. combined mode - Proxy configuration and run timeout Typical ranges per run: - Small (1–3 cities): 20–100 hospitals with emails - Medium (5–15 cities): 200–600 - Large (20+ cities/states): 800–1,000+ Run multiple times across different regions to continuously grow your hospital procurement list without hitting hard platform limits. *** #### πŸ”Œ Integrations & Export Options Once your run completes, you can: - JSON: Full structured data download - CSV / Excel: Import directly into spreadsheets - Apify API: Stream results into your own apps or workflows from the hospital procurement email scraper - Zapier / Make: Trigger automations when new leads are found - Webhooks: Push results to your CRM or pipeline on run completion Plug directly into Instantly, Smartlead, Apollo, HubSpot, Salesforce, or any outreach platform that accepts CSV/JSON imports. Ideal for ops teams that treat this as a hospital procurement data scraper feeding downstream systems. *** #### πŸ› οΈ Step-by-Step Usage Guide - Step 1 β€” Log in to Apify Create a free account or sign in at apify.com. - Step 2 β€” Open the Actor Search for "Hospital Procurement Email Scraper" in the Apify Store and click Try for free. - Step 3 β€” Set Your Search Term Enter "Hospital Procurement" or a variant like "hospital purchasing", "healthcare supply chain", or "materials management". - Step 4 β€” Add Target Locations Enter one or more cities/states β€” e.g., "New York", "Austin, Texas". - Step 5 β€” Set Your Limit Choose how many hospitals with emails you want β€” 20 for a quick test, up to 1,000 for a full campaign. - Step 6 β€” Choose Scaling Strategy Combined cap: The total across all locations combined Per-location cap: Applies your limit independently to each city - Step 7 β€” Enable Proxies Turn on Apify Proxy for stable, uninterrupted crawling at scale. - Step 8 β€” Run πŸš€ Click Start and let the hospital procurement email scraper do the work. - Step 9 β€” Export Download as JSON, CSV, or Excel β€” or pull via API straight into your stack. *** #### βš–οΈ Legal & Compliance This actor collects only publicly available business contact information β€” emails and phone numbers published openly on websites. Best practices to stay compliant: - Only use publicly visible contact data - Do not bypass login walls or paywalls - Respect each website's robots.txt and Terms of Service - Include an unsubscribe option in all outreach - Follow applicable laws in your jurisdiction Relevant regulations to be aware of: - GDPR (EU) - CAN-SPAM Act (US) - CASL (Canada) - PECR (UK) This tool is intended for ethical business prospecting only. You are responsible for how you use the data collected with this hospital procurement email extractor. *** #### ❓ Frequently Asked Questions Q: Does this scrape private or personal emails?\ A: No. The actor only extracts emails that are publicly visible on hospital websites β€” procurement inboxes, purchasing contacts, and general vendor-relations addresses. Q: Can I search multiple cities in one run?\ A: Yes. Add as many locations as needed. Use per-location capping for even geographic distribution of hospital procurement leads. Q: Does it deduplicate results?\ A: Yes. Emails are deduplicated per domain to keep your hospital procurement list accurate. Q: Can I schedule recurring runs?\ A: Absolutely. Use Apify's scheduler to run weekly or monthly and keep your pipeline fresh β€” great for a hospital procurement contact scraper feeding your CRM. Q: What niches does the search term support?\ A: Any Google Maps searchable term β€” try "hospital procurement", "hospital purchasing", "healthcare supply chain", "materials management", or "vendor registration". Q: Are proxies required?\ A: Not for small runs, but strongly recommended for 200+ hospital runs to avoid rate limits and improve stability in your hospital procurement lead finder workflow. Q: How is this different from manual research?\ A: Manual search is slow and inconsistent. This automates discovery, crawl, and extraction β€” acting as a hospital procurement email finder and hospital procurement contact finder in minutes. Q: Can agencies white-label or resell this?\ A: Yes. Run it on behalf of clients and deliver fresh hospital procurement leads on a recurring basis. *** #### πŸ§‘β€πŸ’» Support & Custom Solutions Have a question, feature request, or need a custom build? We’re happy to help with: - Custom input/output configurations - Niche-specific adaptations (e.g., device category or region) - Bulk or enterprise run support - Integration assistance (CRM, marketing automation, data warehouse) Email: scrapermindapi@gmail.com Built for vendors, distributors, and outreach teams who need accurate hospital procurement leads at scale β€” fast. For any help or custom solution, contact via this mail: scrapermindapi@gmail.com # Actor input Schema ## `googleMapsSearchTerm` (type: `string`): Enter the business type or niche for email scraper (e.g., 'coffee shops', 'dentists'). ## `googleMapsLocation` (type: `array`): Target geographic location for the email scraper (e.g., 'Miami, Florida'). ## `maxBusinesses` (type: `integer`): Target number of businesses to find (1-1000). The scraper will stop when this target is reached. ## `scrapeMaxBusinessesPerLocation` (type: `boolean`): If enabled, the scraper will collect up to `maxBusinesses` results per location. If disabled, it combines all locations up to a single total limit. ## `proxyConfiguration` (type: `object`): Proxy settings for scraping. Recommended for large-scale scraping. ## Actor input object example ```json { "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": [ "New York" ], "maxBusinesses": 5, "scrapeMaxBusinessesPerLocation": false, "proxyConfiguration": { "useApifyProxy": true } } ``` # 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 = { "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": [ "New York" ], "maxBusinesses": 5, "proxyConfiguration": { "useApifyProxy": true } }; // Run the Actor and wait for it to finish const run = await client.actor("contacts-api/hospital-procurement-email-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 = { "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": ["New York"], "maxBusinesses": 5, "proxyConfiguration": { "useApifyProxy": True }, } # Run the Actor and wait for it to finish run = client.actor("contacts-api/hospital-procurement-email-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 '{ "googleMapsSearchTerm": "Hospital Procurement", "googleMapsLocation": [ "New York" ], "maxBusinesses": 5, "proxyConfiguration": { "useApifyProxy": true } }' | apify call contacts-api/hospital-procurement-email-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=contacts-api/hospital-procurement-email-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "Hospital Procurement Email Scraper", "description": "Hospital procurement email scraper to extract verified procurement, purchasing, and supply chain contact emails from hospitals, healthcare systems, and medical organizations πŸ“§πŸ₯ Perfect for vendor outreach, healthcare sales, and medical procurement lead generation.", "version": "1.0", "x-build-id": "hPWboTjbSkgRMTdw0" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/contacts-api~hospital-procurement-email-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-contacts-api-hospital-procurement-email-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/contacts-api~hospital-procurement-email-scraper/runs": { "post": { "operationId": "runs-sync-contacts-api-hospital-procurement-email-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/contacts-api~hospital-procurement-email-scraper/run-sync": { "post": { "operationId": "run-sync-contacts-api-hospital-procurement-email-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": [ "googleMapsLocation", "googleMapsSearchTerm" ], "properties": { "googleMapsSearchTerm": { "title": "Search Term", "type": "string", "description": "Enter the business type or niche for email scraper (e.g., 'coffee shops', 'dentists').", "default": "Hospital Procurement" }, "googleMapsLocation": { "title": "Location", "type": "array", "description": "Target geographic location for the email scraper (e.g., 'Miami, Florida').", "default": [ "New York" ], "items": { "type": "string" } }, "maxBusinesses": { "title": "Maximum Businesses With Emails", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Target number of businesses to find (1-1000). The scraper will stop when this target is reached.", "default": 5 }, "scrapeMaxBusinessesPerLocation": { "title": "Scrape Max Businesses Per Location", "type": "boolean", "description": "If enabled, the scraper will collect up to `maxBusinesses` results per location. If disabled, it combines all locations up to a single total limit.", "default": false }, "proxyConfiguration": { "title": "Proxy Configuration", "type": "object", "description": "Proxy settings for scraping. Recommended for large-scale scraping." } } }, "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 } } } } } } } } } } ```