# NL Parking Rates & Live Availability Monitor (`codeclouds/nl-parking-monitor`) Actor Clean, structured parking data for the Netherlands: current tariffs and real-time free-space counts per facility, sourced from RDW's national Open Parkeerdata feed. Detects when a garage's live status changes between runs. - **URL**: https://apify.com/codeclouds/nl-parking-monitor.md - **Developed by:** [Dennis](https://apify.com/codeclouds) (community) - **Categories:** Travel, Lead generation - **Stats:** 2 total users, 0 monthly users, 75.0% runs succeeded, 0 bookmarks - **User rating**: No ratings yet ## Pricing from $3.00 / 1,000 parking-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 ## NL Parking Rates & Live Availability Monitor ๐Ÿ…ฟ๏ธ Clean, structured **parking data for the Netherlands**: current tariffs and real-time free-space counts per facility, straight from RDW's national **Open Parkeerdata** feed (Nationaal Parkeer Register). Detects when a garage's live status changes between runs, so you can build alerts, not just dumps. No login, no API key โ€” this is the same open, government-published feed used by NL parking apps and navigation systems. ### Why this actor? The raw source feed is genuinely painful to work with: every tariff rule is repeated **once per weekday** (a simple hourly rate becomes 7 near-identical records), timestamps are Unix epoch seconds, capacity is sometimes only available in a completely separate live-status endpoint, and addresses are buried several levels deep. This actor does that cleanup for you: - ๐Ÿงน **Tariff simplification** โ€” the 7x weekday-duplicated raw entries are collapsed into one rule per unique price structure, with a computed โ‚ฌ/hour rate and a `free` / `metered` / `daily_cap` classification - ๐ŸŸข **Live availability, normalized** โ€” free spaces, occupancy %, and a plain `available` / `nearly_full` / `full` / `closed` status, not raw booleans you have to interpret - ๐Ÿ”” **Change detection** โ€” remembers each facility's status from the previous run and flags `status_changed` when it flips (e.g. `available` โ†’ `full`), so scheduled monitoring runs give you alerts, not noise - ๐Ÿ“ **Resolved address & coordinates** โ€” pulled from the facility's actual entrance, not the operator's town-hall mailing address - ๐Ÿ›ก๏ธ **Stale-data awareness** โ€” expired tariff periods are dropped rather than reported as current, and `staticDataLastUpdated` tells you how fresh each record is Only about 526 of the ~14,870 facilities in the feed publish live occupancy; the rest have tariffs only (mostly street parking and P+R zones). The actor tells you which is which per record (`hasRealtimeData`). ### When should an AI agent use this? - "How much does it cost to park at parkeergarage Forum in Groningen right now, and are there free spaces?" - "Is there still availability in a parking garage in Rotterdam I can drive to now?" - "Alert me when a specific garage's status flips from available to full." - "Compare the hourly parking rate across garages in a city before I decide where to park." - "Which parking facilities in this feed actually report live occupancy, and which only have tariff info?" - "Find the facility ID for a garage by name so I can monitor it in future runs." ### What data do you get? ```json { "identifier": "9f89a6c7-df06-45ea-adf6-0b94088fcb57", "name": "parkeergarage Forum", "operatorName": "Groningen", "address": { "street": "Schoolstraat", "houseNumber": "16", "zipcode": "9712JS", "city": "Groningen", "province": "" }, "location": { "lat": 53.219207, "lon": 6.57081 }, "usage": "Garage parkeren", "capacity": 325, "evLaadpuntenCapaciteit": 10, "tariffs": [ { "description": "Garagetarief (1,00 euro/18 min)", "kind": "metered", "days": ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun"], "validFrom": "00:00", "validUntil": "23:59", "rates": [{ "chargeEuro": 1, "chargePeriodMinutes": 18, "pricePerHourEuro": 3.33, "durationFromMinutes": 0, "durationUntilMinutes": null }] }, { "description": "Garagetarief (24,00 euro/1440 min)", "kind": "daily_cap", "days": ["Mon", "Tue", "Wed", "Thu", "Fri", "Sat", "Sun"], "validFrom": "00:00", "validUntil": "23:59", "rates": [{ "chargeEuro": 24, "chargePeriodMinutes": 1440, "pricePerHourEuro": 1, "durationFromMinutes": 0, "durationUntilMinutes": null }] } ], "hasRealtimeData": true, "realtime": { "open": true, "full": false, "capacity": 325, "vacantSpaces": 67, "occupancyPercent": 79.4, "status": "available", "lastUpdated": "2026-07-09T14:17:44.000Z" }, "changeType": "unchanged", "previousStatus": "available", "sourceUrls": { "static": "https://npropendata.rdw.nl/...", "dynamic": "https://npropendata.rdw.nl/..." } } ```` ### Use cases - **Parking-finder apps & dashboards** โ€” one clean call per facility gets you tariff and live availability together, ready to render - **"Notify me when it's full" alerts** โ€” schedule runs with `detectChanges` on and route `status_changed` records to Slack/e-mail via Apify integrations - **Price comparison** โ€” compare `pricePerHourEuro` across garages in a city before you drive there - **AI agents & MCP tools** โ€” flat, predictable JSON with a small, well-described input schema; a single call returns everything needed to answer "is there parking near X, and what does it cost right now?" - **Facility discovery** โ€” leave `query`/`facilityIds` empty to browse a sample of facilities with live data, then narrow down by name ### Quick start **Zero-config**: returns the first 25 facilities that publish live occupancy, no input needed. **Search by name:** ```json { "query": "Groningen", "maxResults": 50 } ``` **Monitor specific garages and alert on status changes:** ```json { "facilityIds": ["9f89a6c7-df06-45ea-adf6-0b94088fcb57", "76825e73-4c8d-4a9c-9061-6284afcd865c"], "detectChanges": true } ``` Schedule this hourly: the first run establishes a baseline, every later run only marks `status_changed` when a garage actually flips between available/full/closed. **Only currently-available garages right now:** ```json { "query": "Rotterdam", "onlyAvailableNow": true, "maxResults": 100 } ``` ### Input reference | Field | Description | |---|---| | `facilityIds` | Exact RDW facility UUIDs to fetch (skips name search) | | `query` | Case-insensitive name search, e.g. a city or garage name | | `onlyWithRealtimeData` | Only facilities with live occupancy (default `true`) | | `onlyAvailableNow` | Only open, non-full facilities (default `false`) | | `maxResults` | Cap on facilities fetched/checked per run (default `25`, max `2000`) | | `detectChanges` | Compare against the previous run and flag status changes (default `true`) | | `trackOccupancyHistory` | Build up an occupancy time series per facility across scheduled runs (default `false`) | | `maxHistoryPoints` | How many past measurements to keep per facility (default `30`) | Note: `maxResults` bounds how many facilities are *fetched*, before filters like `onlyAvailableNow` are applied โ€” so the final output can be smaller than the cap. This keeps run cost predictable instead of crawling the full ~14,870-facility index looking for matches. ### Pricing Pay per event: regular facility records are billed at the base `parking-result` rate; a detected **`availability-change-alert`** (a facility's live status actually changed since the last run) is billed at a higher rate โ€” you pay more for genuine insight than for a plain snapshot. When `trackOccupancyHistory` is enabled, each facility that gets a new history point is additionally billed at the **`occupancy-history-point`** rate ($0.005) โ€” this only applies to facilities with real-time data. ### Data source & reliability - Source: RDW's **Open Parkeerdata** (Nationaal Parkeer Register), the Dutch government's public parking-data standard (SPDP2.0) โ€” [data.overheid.nl](https://data.overheid.nl), CC-BY licensed - No authentication required; this actor respects the source's rate limiting with automatic backoff and retry - One broken facility lookup never fails the whole run โ€” errors are collected per facility in the run's key-value store (`RUN_SUMMARY`) - Facility metadata (name, operator, address) is business/government data โ€” no personal data is collected ### FAQ **Why doesn't every facility have live availability?** Only municipalities/operators that have installed occupancy sensors publish a `dynamicDataUrl`. About 526 of ~14,870 facilities currently do โ€” mostly larger garages in bigger cities. Facilities without it still return full tariff information. **Why is a facility's tariff list empty?** Its published validity period has expired in the source data. Rather than show stale pricing, the actor drops it โ€” check `staticDataLastUpdated` for freshness. **How do I find a facility's ID?** Run once with a `query` (e.g. a city name) and no `facilityIds` โ€” the returned `identifier` field is reusable in future runs. **Where is the change-detection history stored?** A compact per-facility status snapshot lives in the actor's key-value store; each run compares against it and updates it. **What does `bezettingsGeschiedenis` contain?** When `trackOccupancyHistory` is enabled, each facility record gets an array of past `{timestamp, occupancyPercent, vacantSpaces}` points (oldest first, capped at `maxHistoryPoints`), built up across scheduled runs via the actor's key-value store. Only facilities with real-time data get history points. ### Related Actors Also by this developer: - **[NL Waterstanden & Watertemperatuur Monitor](../nl-waterstanden-monitor)** โ€” same profile: a real-time Dutch open-government-data monitoring feed, no login/API key required. - **[PDOK Adres Geocoding & Buurtdata](https://apify.com/codeclouds/pdok-locatieserver)** โ€” geocode parking facility addresses to get coordinates and neighbourhood context. - **[NL Milieuzones & Zero-Emissiezones Monitor](https://apify.com/codeclouds/nl-emissiezones-monitor)** โ€” same profile: a direct, authentication-free NDW road-traffic-data feed, no scraping involved. - **[NL Ziekenhuis Wachttijden Monitor](https://apify.com/codeclouds/nl-ziekenhuis-wachttijden-monitor)** โ€” same profile: a direct, authentication-free Dutch government REST feed, no scraping involved. *** *Keywords: nederland parkeren, parkeertarieven, parkeergarage beschikbaarheid, real-time parking availability netherlands, RDW open data, nationaal parkeer register, parking API netherlands, MCP parking tool.* ### Keywords netherlands, parking, parking-rates, parking-availability, open-data, rdw, real-time, mcp-tool ### Changelog #### 0.3.2 - Bugfix - The change-detection snapshot is now merged with the previous run's snapshot instead of being fully replaced, matching the occupancy-history store's existing merge behaviour. Previously, running the actor with a different `query`/`facilityIds` between scheduled runs could wipe the tracked status of facilities left out of that run, causing a later run to miss a real `availability-change-alert`. #### 0.3.1 - Bugfix - Fixed `status_changed` detection and `trackOccupancyHistory` never seeing prior-run state: the actor was reading/writing its snapshot/history to Apify's per-Run *default* key-value store, which is not shared between separate runs. Now uses a named, persistent key-value store. A new baseline will be captured on the next run. #### 0.3.0 - Added `trackOccupancyHistory` (opt-in) โ€” builds up an occupancy time series per facility across scheduled runs, exposed as `bezettingsGeschiedenis`. New `occupancy-history-point` event ($0.005), only charged for facilities with real-time data that got a new point this run. #### 0.2.0 - Added `evLaadpuntenCapaciteit` โ€” EV-charging-point capacity, extracted separately from the general `capacity` field (which some facilities' static feed conflates with EV capacity). `null` when no specification has a `chargingPointCapacity` value; `0` is a real "no EV charging points" value, not an absence. No pricing change. #### 0.1.0 - Initial release - Tariff simplification (weekday-duplicated rules collapsed into unique price structures with computed โ‚ฌ/hour rate) - Live availability normalization (`available` / `nearly_full` / `full` / `closed`) - Change detection between runs (`status_changed` alerts via Pay-Per-Event) - Facility search by name (`query`) or exact `facilityIds` # Actor input Schema ## `facilityIds` (type: `array`): Exact RDW facility identifiers (UUIDs) to fetch, e.g. \["c496f775-0b16-4f5e-8f7a-1a2b3c4d5e6f"]. Skips the name search entirely. Leave empty to search by name/query instead. ## `query` (type: `string`): Case-insensitive text match against the facility name, e.g. "Groningen" or "Forum". Ignored if Facility IDs is set. Leave empty to browse all facilities. ## `onlyWithRealtimeData` (type: `boolean`): Only include facilities that publish real-time free-space counts (about 526 of the ~14,870 in the feed). Turn off to also include tariff-only facilities such as street parking and P+R. ## `onlyAvailableNow` (type: `boolean`): Only keep facilities that are open right now and not full. Requires live occupancy data; facilities without it are excluded when this is on. ## `maxResults` (type: `integer`): Caps how many facilities are fetched and checked in this run (1-2000). Filters like "Only currently available" are applied after fetching, so the final output can be smaller than this number. ## `detectChanges` (type: `boolean`): Compare each facility's live status against the previous run and flag ones that changed (e.g. available -> full). Charged at the higher "availability-change-alert" rate; unchanged/first-seen facilities are charged the standard rate. ## `trackOccupancyHistory` (type: `boolean`): Build up an occupancy time series per facility across scheduled runs (stored in the actor's key-value store), capped at maxHistoryPoints. Only applies to facilities with real-time data. Charges a new occupancy-history-point event per facility that gets a new point. ## `maxHistoryPoints` (type: `integer`): How many past measurements to keep per facility when trackOccupancyHistory is enabled. Oldest points are dropped once this cap is reached. ## Actor input object example ```json { "facilityIds": [], "onlyWithRealtimeData": true, "onlyAvailableNow": false, "maxResults": 25, "detectChanges": true, "trackOccupancyHistory": false, "maxHistoryPoints": 30 } ``` # 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 = {}; // Run the Actor and wait for it to finish const run = await client.actor("codeclouds/nl-parking-monitor").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 = {} # Run the Actor and wait for it to finish run = client.actor("codeclouds/nl-parking-monitor").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 '{}' | apify call codeclouds/nl-parking-monitor --silent --output-dataset ``` ## MCP server setup ```json { "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/?tools=codeclouds/nl-parking-monitor", "--header", "Authorization: Bearer " ] } } } ``` ## OpenAPI specification ```json { "openapi": "3.0.1", "info": { "title": "NL Parking Rates & Live Availability Monitor", "description": "Clean, structured parking data for the Netherlands: current tariffs and real-time free-space counts per facility, sourced from RDW's national Open Parkeerdata feed. Detects when a garage's live status changes between runs.", "version": "0.1", "x-build-id": "pBJQf9ednDvL9BNqs" }, "servers": [ { "url": "https://api.apify.com/v2" } ], "paths": { "/acts/codeclouds~nl-parking-monitor/run-sync-get-dataset-items": { "post": { "operationId": "run-sync-get-dataset-items-codeclouds-nl-parking-monitor", "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/codeclouds~nl-parking-monitor/runs": { "post": { "operationId": "runs-sync-codeclouds-nl-parking-monitor", "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/codeclouds~nl-parking-monitor/run-sync": { "post": { "operationId": "run-sync-codeclouds-nl-parking-monitor", "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": { "facilityIds": { "title": "Facility IDs", "type": "array", "description": "Exact RDW facility identifiers (UUIDs) to fetch, e.g. [\"c496f775-0b16-4f5e-8f7a-1a2b3c4d5e6f\"]. Skips the name search entirely. Leave empty to search by name/query instead.", "default": [], "items": { "type": "string" } }, "query": { "title": "Name search", "type": "string", "description": "Case-insensitive text match against the facility name, e.g. \"Groningen\" or \"Forum\". Ignored if Facility IDs is set. Leave empty to browse all facilities." }, "onlyWithRealtimeData": { "title": "Only facilities with live occupancy", "type": "boolean", "description": "Only include facilities that publish real-time free-space counts (about 526 of the ~14,870 in the feed). Turn off to also include tariff-only facilities such as street parking and P+R.", "default": true }, "onlyAvailableNow": { "title": "Only currently available", "type": "boolean", "description": "Only keep facilities that are open right now and not full. Requires live occupancy data; facilities without it are excluded when this is on.", "default": false }, "maxResults": { "title": "Max facilities", "minimum": 1, "maximum": 2000, "type": "integer", "description": "Caps how many facilities are fetched and checked in this run (1-2000). Filters like \"Only currently available\" are applied after fetching, so the final output can be smaller than this number.", "default": 25 }, "detectChanges": { "title": "Detect availability changes", "type": "boolean", "description": "Compare each facility's live status against the previous run and flag ones that changed (e.g. available -> full). Charged at the higher \"availability-change-alert\" rate; unchanged/first-seen facilities are charged the standard rate.", "default": true }, "trackOccupancyHistory": { "title": "Track occupancy history", "type": "boolean", "description": "Build up an occupancy time series per facility across scheduled runs (stored in the actor's key-value store), capped at maxHistoryPoints. Only applies to facilities with real-time data. Charges a new occupancy-history-point event per facility that gets a new point.", "default": false }, "maxHistoryPoints": { "title": "Max history points per facility", "minimum": 1, "maximum": 200, "type": "integer", "description": "How many past measurements to keep per facility when trackOccupancyHistory is enabled. Oldest points are dropped once this cap is reached.", "default": 30 } } }, "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 } } } } } } } } } } ```