An Access Token is a secure, unique key used to authenticate and control access to Fetchify’s APIs and integrations.

Every API request made to Fetchify must include a valid access token. This allows Fetchify to identify who is making the request, what they are allowed to use, and how that usage should be measured and billed.

What a Fetchify Access Token does

A Fetchify access token governs four core areas:

1. Product access control

Each token is explicitly configured to allow access to specific Fetchify products, such as:

• UK Address Lookup
• International Address Validation
• Email Validation
• Phone Validation
• Bank Account Validation

Requests made to products not enabled on the token are rejected automatically.

This prevents accidental or unauthorised usage and allows fine-grained control across different environments or applications.

2. Geocode availability

Geospatial data access is controlled at token level.

Depending on how the token is configured, responses may include:

• No geocodes
• Approximate geocodes
• Rooftop-level latitude and longitude

This ensures customers only receive the level of location precision they are licensed for, while maintaining compliance with data licensing terms.

3. Usage tracking and analytics

Every request made using an access token is logged against that token.

This enables:

• Accurate usage reporting
• Per-integration or per-environment monitoring (for example, website checkout vs internal CRM)
• Detection of unusual spikes or misuse
• Clear visibility for customers into how and where their credits are being consumed

Because usage is token-specific, Fetchify can provide precise, auditable reporting rather than blended account-level estimates.

4. Billing and credit enforcement

Access tokens are directly linked to billing logic.

They determine:

• Which subscription, licence, or credit pack usage is deducted from
• When usage limits are reached
• When requests should be throttled or rejected due to insufficient balance

This ensures customers are only billed for actual, authorised usage, and prevents unexpected overages.

Why Fetchify uses access tokens (rather than shared keys)

Using token-based access allows Fetchify customers to:

• Separate production, staging, and test environments
• Rotate or revoke access without impacting other systems
• Assign different permissions to different integrations
• Maintain security without embedding account-level credentials in code

It also allows Fetchify to evolve products and pricing without breaking existing integrations.