Show the calling account
/account
Returns the account that this API key belongs to, including the environment, the products
the account can use, and the current billing balance.
This is the recommended first call for any new integration: it lets you confirm that your
credentials work, that you are pointed at the expected environment (live or sandbox),
and that the products you intend to use are enabled on the account.
Example Request
GETRequest Schema
Available Response Data
13 Data Pointsuuid uuid
The account's UUID
account_name string
The display name of the account
company_name string
The legal/company name on file for the account
environment enum (Which environment this account (and any keys on it) operate in: live, sandbox)
is_reseller boolean (Whether this account is a reseller (i.e. has sub accounts under it))
parent_account_uuid uuid
The UUID of the parent account when this account is a sub account of a reseller
expires_at timestamp
ISO 8601 timestamp at which the account is scheduled to expire
data_retention_days integer
Account-level data retention in days
balance string
Current cash balance for the billing account, as a decimal string with 4 decimal
credit_limit string
Credit limit for the billing account, as a decimal string with 4 decimal places
available_credit string
Convenience field equal to balance + credit_limit, expressed as a decimal string
products array
The list of products this account can actually use
api_reference uuid
unique request identifier for log tracing and audit
API Data Scale & Coverage tag
Unmatched data depth to power your compliance and verification workflows.
Sandbox Environment
Build and test against a sandbox account. Sandbox is a separate account with its own UUID and its own API keys, and the environment is fixed at the account level, so you cannot switch an existing key between live and sandbox with a parameter or header. Both share the same base URL, so the account behind your key is what determines which environment you are in. GET /v1/account returns an environment field of live or sandbox, and that is the authoritative answer.
Calls on a sandbox key are not billed. Every endpoint, response shape, error envelope, idempotency and rate-limit behaviour mirrors live, so the only change when you move to production should be the credentials. Sandbox accounts are provisioned by your Global Data account manager.
Technical Use Cases tag
Detail view in your own UI
Fetch the full account record by UUID to render a detail screen inside your own application, so staff never need a second system open.
Evidence for a decision record
Retrieve the stored account at the point a decision is made and attach it to your case file, with the api_reference value recorded for log tracing.
Support and reconciliation
Resolve a single UUID when investigating a discrepancy, without paging a list endpoint to find it.
Compliance & Security tag
Enterprise-grade infrastructure audited against the standards your regulators require.
Common Questions tag
Everything you need to know about implementation details and compliance infrastructure.
rocket_launch Implementation
What are the rate limits?
add
What are the rate limits?
600 requests per minute by default, enforced with a 60-second fixed window. Every response carries X-RateLimit-Limit and X-RateLimit-Remaining.
Exceeding the limit returns 429 Too Many Requests with a Retry-After header giving the number of seconds to wait, and X-RateLimit-Reset giving the reset timestamp. Schedule retries from Retry-After instead of a fixed sleep, and slow down before you hit zero, not after.
Higher limits can be arranged case by case through WatchEye support.
Ready to integrate Show the calling account?
Talk to our team about credentials, sandbox access and the right combination of endpoints for your workflow.