API Keys

Generate and manage API keys to connect Volume Reach to your own systems and workflows programmatically.

Overview

API keys allow external applications and automation tools to interact with your Volume Reach account without requiring a manual login. This enables your development team to build custom integrations, trigger campaigns automatically, pull reporting data into your own dashboards, and more.

API key access is available exclusively on the Scale plan.

How It Works

Navigate to Settings > API Keys to manage your keys.

Generating a New API Key

Go to Settings > API Keys.
Click Generate New Key.
Give the key a descriptive name so you can identify its purpose later (for example, "CRM Integration" or "Reporting Dashboard").
Click Create.
Copy the key immediately and store it somewhere secure. Volume Reach will not display the full key again after you leave this screen.

Managing Existing Keys

Your API Keys page lists all keys you have created, along with their names and creation dates. From this page you can:

Revoke a key — Immediately disables the key. Any integration using that key will stop working until it is updated with a new key.
Rename a key — Update the display name to keep your list organized.

Revoking a key cannot be undone. You will need to generate a new key and update your integration if you revoke one by mistake.

Using an API Key

Include your API key in the request headers when making calls to the Volume Reach API. Refer to the API reference documentation for full details on available endpoints and authentication headers.

Tips & Best Practices

Create one key per integration. Using separate keys for each system makes it easy to revoke access for a single integration without disrupting others.
Never expose your API key publicly. Do not include it in client-side code, public repositories, or anywhere it could be seen by unauthorized parties.
Rotate keys periodically. Generating a new key and retiring old ones reduces the risk of a compromised key going unnoticed.
Name keys clearly. A descriptive name like "Zapier Automation" or "Internal Reporting Tool" makes it easy to identify what each key is for when you need to manage or revoke it.
Revoke unused keys promptly. If an integration is retired or a team member who managed it leaves, revoke their associated key immediately.