How to Create API Keys

API keys allow you to connect your Recruitly account with external tools, Chrome extensions, automation platforms like Zapier, and custom-built applications.

What is an API Key?

An API key is a unique identifier that authenticates your requests to the Recruitly API. It provides the same access level as your user account, allowing you to read and write data across all modules — candidates, contacts, companies, jobs, leads, and more.

Creating an API Key

Step-by-Step

1. Log in to your Recruitly account
2. Click your profile avatar in the top-right corner of the screen
3. Select My Profile from the dropdown menu
4. Navigate to the API Keys tab
5. Click the “Generate New Key” button
6. Copy the key immediately — for security reasons, it cannot be retrieved later

What You Can Do with Your API Key

• Connect the Recruitly Chrome Extension for seamless browser-based sourcing
• Set up Zapier workflows to automate data sync between Recruitly and other tools
• Build custom integrations that create candidates, search jobs, update contacts, and more
• Power AI assistants through the MCP integration
• Generate reports and analytics from your recruitment data

Managing Your API Keys

Adding Labels

Give each key a descriptive label so you can easily identify which integration it belongs to. Click “Add Label” on any key row and enter a name like “Chrome Extension”, “Zapier”, or “Internal Dashboard”.

Disabling a Key

If you no longer need a key or suspect it has been compromised:

1. Find the key in your list
2. Click the “Disable” button on that row
3. The key will stop working immediately

Disabled keys are moved to the Disabled tab. You can re-enable them at any time.

Re-enabling a Key

1. Switch to the Disabled tab
2. Find the key you want to reactivate
3. Click “Enable” to restore access

Best Practices

• One key per integration — Generate a separate key for each tool or application. This way, if one key is compromised, you can disable it without affecting your other integrations.
• Keep keys secret — Never share your API key publicly, paste it in emails, or commit it to source control (e.g., GitHub).
• Label everything — Add a label to every key so you know exactly what it’s used for, even months later.
• Disable unused keys — If you stop using an integration, disable its key right away. You can always re-enable it later.
• Act fast if compromised — If you suspect a key has been exposed, disable it immediately and generate a new one.

Frequently Asked Questions

Can I have multiple API keys?
Yes. You can generate as many keys as you need — we recommend one per integration.

What happens if I disable a key?
Any integration using that key will immediately lose access. API requests with a disabled key will return a 401 Unauthorized error.

Can I see the full key after generating it?
API keys are shown only once at the time of creation — make sure to copy them immediately.

Do API keys expire?
No, API keys remain active until you manually disable them.