account/data_tokens
Tool: read
Get the shared Data Token balance and per-service usage rates. Data Tokens are prepaid credits that pay for email validation and enrichment (1 token = 1 validation result) — they are not the email personalization vocabulary, which this operation does not expose — that lives in personalization-variables. Check the balance before submitting a large validation batch.
The balance is shared across the billing account. The monthly-limit fields describe the calling
clientspace and are null when no monthly limit applies. services[] lists what Data Tokens can be
spent on (including planned services) with their per-unit price.
Response
200 — Data Token status.
| field | type | description |
|---|---|---|
| balance | integer | Current spendable Data Token balance for the billing account. |
| monthlyLimit | integer | Monthly Data Token limit for this clientspace; null when no monthly limit applies. |
| usedThisMonth | integer | Data Tokens used by this clientspace in the current UTC month; null when no monthly limit applies. |
| remainingThisMonth | integer | Remaining monthly Data Tokens for this clientspace; null when no monthly limit applies. |
| services[] | array | Current and planned services that use Data Tokens. |
| services[].service | string | Machine-readable service key. |
| services[].label | string | Human-readable service label. |
| services[].tokensPerUnit | integer | Data Tokens charged per unit. |
| services[].unit | string | Unit the token price applies to. |
| services[].status | string | Optional lifecycle status, e.g. planned. |
Errors: 400, 401, 403, 406, 422, 429, 500 — shared schema: schemas/errors.
Invoke
Call read with name: "account/data_tokens".