# TickPick Events & Tickets Scraper (`automation-lab/tickpick-events-tickets-scraper`) Actor 🎟️ Extract public TickPick events, performers, schedules, venues, availability, and aggregate ticket prices. Export JSON, CSV, or Excel; schedule runs or use the API. - **URL**: https://apify.com/automation-lab/tickpick-events-tickets-scraper.md - **Developed by:** [Stas Persiianenko](https://apify.com/automation-lab) (community) - **Categories:** Travel - **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing Pay per event This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events. Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have. 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 ## TickPick Events & Tickets Scraper Turn public TickPick pages into structured event and ticket-price data. Use direct event URLs, discovery pages, or search terms. Get event IDs, schedules, performers, venues, availability, currencies, and current aggregate low/high prices in one clean dataset. The Actor is designed for repeatable ticket-market research, event enrichment, and price monitoring without checkout automation or account access. ### What does TickPick Events & Tickets Scraper do? The Actor visits public pages on TickPick and extracts normalized event records. It supports: - 🎟️ Direct TickPick event URLs - πŸ”Ž TickPick search queries - 🏟️ Venue, performer, city, category, sport, concert, and theater discovery pages - πŸ’΅ Current aggregate low and high ticket prices - πŸ“ Venue names and public address fields - 🎀 Performer names - πŸ“… Event start and end times when published - βœ… Ticket availability and offer-validity timestamps Discovery pages are followed to event detail pages. Duplicate event links are merged using the numeric TickPick event ID. ### Who is it for? #### Ticket-market analysts Track public price ranges across events and compare changes between scheduled runs. #### Event aggregators Enrich calendars with performers, venue details, images, and source URLs. #### Travel and entertainment apps Add upcoming events near destinations and let users follow the original TickPick page. #### Sports researchers Collect schedules and aggregate ticket-price signals for teams, leagues, and venues. #### Data teams Export consistent JSON, CSV, Excel, XML, or RSS-compatible data from Apify datasets. ### Why use this Actor? TickPick pages are useful to people but awkward to combine at scale. This Actor converts the public structured information into stable records. Benefits include: - ⚑ HTTP-first extraction without a heavy browser runtime - 🧩 Consistent fields across event types - πŸ” Repeatable runs for monitoring - πŸ›‘οΈ Same-host URL validation - ♻️ Event-ID deduplication - πŸ“¦ Native Apify datasets and API access - πŸ”Œ Integrations with webhooks, Make, Zapier, Google Sheets, and cloud storage ### What TickPick data can I extract? | Field | Description | |---|---| | `eventId` | Numeric TickPick event identifier | | `url` | Canonical public TickPick event URL | | `title` | Event title | | `description` | Public event summary when available | | `eventType` | Schema.org event type, such as `MusicEvent` | | `eventStatus` | Scheduled, cancelled, postponed, or another published status | | `startTime` | Published event start time | | `endTime` | Published event end time when available | | `performers` | List of published performer names | | `primaryPerformer` | First published performer | | `venueName` | Venue name | | `venueUrl` | Public TickPick venue URL | | `streetAddress` | Venue street address | | `city` | Venue city | | `region` | State or region | | `country` | Country code or name | | `imageUrl` | Public event or performer image | | `availability` | Published ticket availability | | `currency` | Price currency, commonly USD | | `lowPrice` | Current aggregate low ticket price | | `highPrice` | Current aggregate high ticket price | | `priceValidFrom` | Beginning of the published price-valid window | | `priceValidThrough` | End of the published price-valid window | | `scrapedAt` | UTC extraction timestamp | Fields absent from the source are omitted instead of filled with misleading values. ### How much does it cost to scrape TickPick events? This Actor uses pay-per-event pricing. You pay a $0.005 start charge and a charge for each event record produced. | Apify tier | Price per event | |---|---:| | Free | $0.00024088 | | Bronze | $0.00020946 | | Silver | $0.00016338 | | Gold | $0.00012568 | | Platinum | $0.000083785 | | Diamond | $0.00005865 | For example, 100 records cost about $0.0291 on Bronze including the start charge. The live price appears in the Actor pricing tab before every run and is authoritative. A five-event test is intentionally available through the input prefill. To estimate a run: 1. Choose the expected number of events. 2. Multiply it by your plan's displayed record price. 3. Add the displayed one-time start charge. 4. Set `maxItems` to enforce a hard record limit. ### How to scrape TickPick event data 1. Open the Actor input page. 2. Add one or more TickPick URLs, search queries, or both. 3. Set a conservative `maxItems` value. 4. Leave proxy access disabled unless direct requests are limited. 5. Click **Start**. 6. Open the **Dataset** tab when the run finishes. 7. Export the results or access them through the API. A direct event URL is the fastest way to test one record. A search query or discovery page is better for collecting several events. ### Input options #### TickPick URLs Add public TickPick URLs using the request-list editor. Supported examples include: - Event detail pages - TickPick search pages - Sports category pages - Concert and theater pages - Performer or team pages - Venue pages - City discovery pages Only `tickpick.com` hosts are accepted. #### Search queries Enter artist, team, venue, city, or event terms. Each value is sent to TickPick's public search page. #### Maximum events `maxItems` limits unique saved event records across all inputs. The default is 25 and the prefilled test uses 5. #### Proxy configuration Direct access is the cheapest default. Enable Apify Proxy or provide custom proxies if TickPick limits requests from your run location. ### Input example ```json { "searchQueries": ["concert"], "startUrls": [ { "url": "https://www.tickpick.com/nfl-tickets/" } ], "maxItems": 10, "proxyConfiguration": { "useApifyProxy": false } } ```` You may use only `searchQueries`, only `startUrls`, or both. At least one route is required. ### Output example ```json { "eventId": "7676474", "url": "https://www.tickpick.com/buy-five-finger-death-punch-cody-jinks-eva-under-fire-tickets-the-cynthia-woods-mitchell-pavilion-9-27-26-6pm/7676474/", "title": "Five Finger Death Punch, Cody Jinks & Eva Under Fire", "eventType": "MusicEvent", "eventStatus": "EventScheduled", "startTime": "2026-09-27T18:45:00", "performers": ["Five Finger Death Punch"], "venueName": "The Cynthia Woods Mitchell Pavilion", "city": "Spring", "region": "TX", "country": "US", "availability": "InStock", "currency": "USD", "lowPrice": 29, "highPrice": 1259, "scrapedAt": "2026-07-16T03:15:00.000Z" } ``` Prices are source observations, not purchase quotes or guarantees. ### Ticket price monitoring workflow Run the Actor on a schedule to build a time series. A practical workflow is: 1. Save stable event or discovery URLs in an Apify task. 2. Schedule the task hourly, daily, or weekly. 3. Keep `eventId`, `lowPrice`, `highPrice`, `availability`, and `scrapedAt`. 4. Append each run to a warehouse or spreadsheet. 5. Alert when the low price crosses a threshold. 6. Follow `url` to verify the live offer before acting. Offer timestamps help distinguish a current source observation from an old export. ### Tips for reliable results - Start with one direct event URL. - Use low `maxItems` values while designing a workflow. - Prefer specific performer, venue, or category pages over broad searches. - Schedule repeated monitoring rather than starting many overlapping runs. - Enable a proxy only after direct access is limited. - Keep the source URL with every downstream record. - Treat missing optional values as unavailable at the source. - Compare prices only when currencies match. ### Integrations #### Google Sheets Use the Apify Google Sheets integration to append price snapshots for analyst review. #### Make Trigger the Actor from Make, iterate over dataset items, and route events by city or price. #### Zapier Send newly discovered events to Slack, email, a CRM, or an internal calendar workflow. #### Webhooks Attach a run-succeeded webhook and fetch the default dataset from your backend. #### Cloud storage Export JSON or CSV to Amazon S3, Google Cloud Storage, Azure, or your data warehouse process. #### Event calendar enrichment Join records by `eventId`, canonical URL, performer, venue, and event time. ### API usage with JavaScript ```javascript import { ApifyClient } from 'apify-client'; const client = new ApifyClient({ token: process.env.APIFY_TOKEN }); const run = await client.actor('automation-lab/tickpick-events-tickets-scraper').call({ searchQueries: ['concert'], maxItems: 10, }); const { items } = await client.dataset(run.defaultDatasetId).listItems(); console.log(items); ``` Use an environment variable for your Apify token. ### API usage with Python ```python from apify_client import ApifyClient import os client = ApifyClient(os.environ['APIFY_TOKEN']) run = client.actor('automation-lab/tickpick-events-tickets-scraper').call( run_input={'searchQueries': ['concert'], 'maxItems': 10} ) items = client.dataset(run['defaultDatasetId']).list_items().items print(items) ``` The dataset remains available according to your Apify storage retention settings. ### API usage with cURL ```bash curl -X POST \ "https://api.apify.com/v2/acts/automation-lab~tickpick-events-tickets-scraper/runs?token=$APIFY_TOKEN" \ -H "Content-Type: application/json" \ -d '{"searchQueries":["concert"],"maxItems":10}' ``` Use the returned run and dataset identifiers to retrieve output. Do not put long-lived tokens into source control. ### Use with AI agents via MCP Connect AI tools through the Apify Model Context Protocol server. The actor-specific endpoint is: `https://mcp.apify.com/?tools=automation-lab/tickpick-events-tickets-scraper` #### Claude Code setup ```bash claude mcp add --transport http apify "https://mcp.apify.com/?tools=automation-lab/tickpick-events-tickets-scraper" ``` Authenticate with your Apify account when prompted. #### Claude Desktop, Cursor, and VS Code setup Add this server to the MCP configuration used by Claude Desktop, Cursor, or VS Code: ```json { "mcpServers": { "apify": { "url": "https://mcp.apify.com/?tools=automation-lab/tickpick-events-tickets-scraper" } } } ``` Example prompts: - β€œUse automation-lab/tickpick-events-tickets-scraper to find ten concert events and compare their aggregate low prices.” - β€œExtract this TickPick event and summarize the venue and schedule.” - β€œBuild a table of NFL events with city, availability, and price range.” Always review live source pages before making purchase or resale decisions. ### Error handling and troubleshooting #### Why did the run report no events? The URL may not currently expose event links, the search may have no matching events, or TickPick may have limited the request. Try one known public event URL first. Then narrow the query or enable proxy access. The Actor intentionally fails instead of returning a misleading empty success when every extraction route fails. #### Why are some fields missing? TickPick does not publish every optional field for every event. The Actor omits unavailable values rather than inventing data. #### Why did my external URL fail? For safety and product consistency, explicit URLs must belong to TickPick. #### Why do prices change between runs? Ticket marketplaces are dynamic. Use `priceValidFrom`, `priceValidThrough`, and `scrapedAt` when comparing snapshots. ### Data quality and limitations The Actor extracts public aggregate event offers. It does not: - Sign in to TickPick - Buy or reserve tickets - Automate checkout - Return seat-level inventory in minimum v1 - Guarantee that a displayed offer remains available - Convert currencies - Predict future ticket prices Source pages and structured markup can change. Validate important decisions against the linked event URL. ### Legality Scraping public web data can be lawful, but requirements vary by country, purpose, contract, and data type. You are responsible for your use of the Actor and resulting data. Review TickPick's terms, applicable laws, database rights, rate limits, and privacy obligations. Avoid collecting personal data, bypassing access controls, or using output for prohibited activities. This documentation is not legal advice. ### FAQ #### Can I scrape one event? Yes. Supply its public TickPick event URL and set `maxItems` to 1. #### Can I search by artist or team? Yes. Put the name in `searchQueries` or provide the relevant TickPick performer or team page. #### Does it return exact seats and rows? No. Minimum v1 focuses on event metadata and public aggregate low/high prices. #### Are duplicate events removed? Yes. Records are deduplicated by TickPick's numeric event ID during each run. #### Can I schedule recurring runs? Yes. Save the input as an Apify task and attach a schedule. #### Can I export CSV or Excel? Yes. Use the dataset export controls or API format parameter. #### Does it require a TickPick account? No. The Actor uses public anonymous event and discovery pages. #### Should I enable a residential proxy? Only if direct requests are consistently limited and your Apify plan permits it. ### Related event scrapers Explore other event workflows from automation-lab: - [Eventbrite Events Scraper](https://apify.com/automation-lab/eventbrite-events-scraper) - [Bandsintown Events Scraper](https://apify.com/automation-lab/bandsintown-events-scraper) - [DICE Events Scraper](https://apify.com/automation-lab/dice-events-scraper) Combine source-specific actors only after normalizing IDs, URLs, times, currencies, and venue names. ### Support If a valid public TickPick page fails, open an Actor issue with: - The input used - The run URL - The expected event - Whether proxy access was enabled - The approximate time of the run Do not include passwords, account cookies, payment details, or private tokens. # Actor input Schema ## `startUrls` (type: `array`): Direct event URLs return one record; discovery URLs are followed to their event pages. ## `searchQueries` (type: `array`): TickPick search terms such as an artist, team, venue, city, or event name. ## `maxItems` (type: `integer`): Stop after this many unique event records have been saved. ## `proxyConfiguration` (type: `object`): Optional Apify Proxy or custom proxy settings. Enable this if TickPick limits requests from your location. ## Actor input object example ```json { "startUrls": [ { "url": "https://www.tickpick.com/buy-five-finger-death-punch-cody-jinks-eva-under-fire-tickets-the-cynthia-woods-mitchell-pavilion-9-27-26-6pm/7676474/" } ], "searchQueries": [ "concert" ], "maxItems": 5, "proxyConfiguration": { "useApifyProxy": false } } ``` # Actor output Schema ## `overview` (type: `string`): No description # 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 = { "startUrls": [ { "url": "https://www.tickpick.com/buy-five-finger-death-punch-cody-jinks-eva-under-fire-tickets-the-cynthia-woods-mitchell-pavilion-9-27-26-6pm/7676474/" } ], "searchQueries": [ "concert" ], "maxItems": 5 }; // Run the Actor and wait for it to finish const run = await client.actor("automation-lab/tickpick-events-tickets-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 = { "startUrls": [{ "url": "https://www.tickpick.com/buy-five-finger-death-punch-cody-jinks-eva-under-fire-tickets-the-cynthia-woods-mitchell-pavilion-9-27-26-6pm/7676474/" }], "searchQueries": ["concert"], "maxItems": 5, } # Run the Actor and wait for it to finish run = client.actor("automation-lab/tickpick-events-tickets-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 '{ "startUrls": [ { "url": "https://www.tickpick.com/buy-five-finger-death-punch-cody-jinks-eva-under-fire-tickets-the-cynthia-woods-mitchell-pavilion-9-27-26-6pm/7676474/" } ], "searchQueries": [ "concert" ], "maxItems": 5 }' | apify call automation-lab/tickpick-events-tickets-scraper --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=automation-lab/tickpick-events-tickets-scraper", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "TickPick Events & Tickets Scraper", "description": "🎟️ Extract public TickPick events, performers, schedules, venues, availability, and aggregate ticket prices. Export JSON, CSV, or Excel; schedule runs or use the API.", "version": "0.1", "x-build-id": "prPeWf8qHwi5HfyMF" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/automation-lab~tickpick-events-tickets-scraper/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-automation-lab-tickpick-events-tickets-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/automation-lab~tickpick-events-tickets-scraper/runs": { "post": { "operationId": "runs-sync-automation-lab-tickpick-events-tickets-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/automation-lab~tickpick-events-tickets-scraper/run-sync": { "post": { "operationId": "run-sync-automation-lab-tickpick-events-tickets-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": { "startUrls": { "title": "TickPick URLs", "type": "array", "description": "Direct event URLs return one record; discovery URLs are followed to their event pages.", "items": { "type": "object", "required": [ "url" ], "properties": { "url": { "type": "string", "title": "URL of a web page", "format": "uri" } } } }, "searchQueries": { "title": "Search queries", "type": "array", "description": "TickPick search terms such as an artist, team, venue, city, or event name.", "items": { "type": "string" } }, "maxItems": { "title": "Maximum events", "minimum": 1, "maximum": 1000, "type": "integer", "description": "Stop after this many unique event records have been saved.", "default": 25 }, "proxyConfiguration": { "title": "Proxy configuration", "type": "object", "description": "Optional Apify Proxy or custom proxy settings. Enable this if TickPick limits requests from your location.", "default": { "useApifyProxy": 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 } } } } } } } } } } ```