Skip to main content

​
Overview

Reevo provides API keys that allow you to connect external tools and automate data flow into your workspace. With API keys, you can push contacts from platforms like Clay or Zapier, build custom integrations, or sync data from your own systems directly into Reevo without manual entry. API keys use a permission-based system, allowing you to control exactly what each key can access. This means you can create separate keys for different integrations with only the permissions they need.

​
Prerequisites

  • You must be an admin in your Reevo workspace to create API keys
  • Your organization must have available quota for public requests

​
Watch: How to Generate and Manage API Keys

​
Step-by-Step Instructions

​
Creating a New API Key

  1. Navigate to Settings in your Reevo workspace
  2. Go to the API Keys section → New API key button Reevo Integration With Other Tools API Keys Location Pn
  3. Give your key a descriptive name (for example, “Clay Integration” or “Zapier Webhook”)
  4. Select the permissions your integration needs:
PermissionsReadWrite
Accounts✓✓
Contacts✓✓
Opportunities✓✓
Tasks✓✓
Users✓X
Mailbox✓X
Sequence Enrollment✓✓
Webhooks✓✓
Read permissions allow an API key to view and retrieve data, but not modify it.  For example, with Accounts Read, you can fetch account information but cannot create or update accounts.Write permissions allow an API key to create, update, or modify data. Importantly, write permissions automatically include read permissions for the same resource. So if you have Contacts Write, you can both read and write contact data without needing to also select Contacts Read.
  1. Click Generate
Important: Copy the API key immediately and store it securely. You will not be able to view it again after closing the popup.

​
Managing Existing API Keys

You can manage Existing API Keys under Setting → Integrations. The API keys table shows:
  • Name: The label you gave the key
  • Permissions: What the key can access
  • Status: Whether the key is Active or Expired
Active keys are listed first, followed by expired keys, sorted alphabetically by name.

​
Expiring an API Key

If you need to revoke access for a key:
  1. Find the key in your API keys table
  2. Click the three-dot menu next to the key
  3. Select Expire key
  4. The key will immediately stop working and show as “Expired” in your table

​
Using Your API Key

When making requests to Reevo, include your API key in the request header:
  • Header name: x-api-key
  • Header value: Your API key
The system automatically validates that your key has the required permissions for each request. If a key lacks necessary permissions, the request will be rejected with a clear error message indicating which permissions are missing.

​
Troubleshooting / FAQs

Only workspace admins can create API keys. If you need access, ask an admin to either grant you admin permissions or create the key for you.
No. For security reasons, API keys are only shown once when created. If you lose a key, you must expire the old one and generate a new one.
Requests using an expired key will be rejected with an “API key has expired” error. You’ll need to generate a new key and update your integration.
Yes, as long as the key has all the permissions needed by each integration. However, for better security and tracking, consider creating separate keys for each integration.
If your key has write access to a resource (like Contacts Write), it automatically includes read access too (Contacts Read). You don’t need to select both.
Your organization has limits on public requests. If you’re approaching or exceeding your quota, contact your account manager to discuss increasing your limits.
Still have questions? Reach out to our support team here