---
title: "Connect Keka Hire to Metaintro | Metaintro"
canonical: "https://www.metaintro.com/help/connect-keka-to-metaintro"
language: "en"
author: "Metaintro"
published: "2026-11-11T16:02:27.684Z"
modified: "2026-11-11T16:02:42.557Z"
---

# Connect Keka Hire to Metaintro

Create a Keka API client and key so people who choose to share with you arrive as candidates on your Keka Hire jobs.

Last updated: November 11, 2026[Employers](/help/category/employers)

Paste it into Claude, ChatGPT, Codex, Cursor or Pi.

## Before you start

Only a Keka Global admin can create API credentials.

The Keka API is an add-on that needs its own subscription. Ask your Keka contact if you do not see API access.

You will paste four things into Metaintro: your Keka company subdomain, a client ID, a client secret and an API key.

## Create the credential in Keka

These steps follow Keka's [getting started guide for customers](https://developers.keka.com/docs/getting-started-for-customers).

1. Sign in to Keka as a Global admin.
2. Go to **Global admin settings > Integrations & Automations > API access > API key**.
3. Generate the client ID and client secret. Copy both.
4. Generate an API key. Select the privileges and scopes for Hire.
5. Optionally, turn on **Set expiry** and choose a date. The connection stops working on that date.
6. Copy the API key.

## Connect in Metaintro

1. In Metaintro, go to **Settings > Integrations**.
2. Choose **Keka Hire**.
3. In **Keka company subdomain**, enter the part before.keka.com in your Keka address.
4. In **Client ID**, paste the client ID.
5. In **Client secret**, paste the client secret.
6. In **API key**, paste the API key.
7. Select **Connect**.

Then map your jobs, set your rules, check the preview and go live.

## What Metaintro sends and reads

Metaintro only sends people who chose to share their profile with you for a specific job.

- **Jobs:** Metaintro reads your Keka Hire jobs so you can map them.
- **Candidate:** Metaintro looks for a candidate with the same email address on the job. If there is none, it adds one to the job with their name and email.
- **Résumé:** uploaded to the candidate when the person has one.
- **Note:** a note on the candidate with the link to their proof card.

Metaintro checks candidates in Keka regularly. While a candidate is active, Metaintro sees only that they are still in progress. When they are archived, Metaintro reads the archive reason: hired, withdrawn, or otherwise not selected.

## Limits

- Keka allows 50 API requests a minute. Metaintro stays below that, so busy times can queue deliveries for a few minutes.
- Keka does not share stage names, so Metaintro cannot show interview or offer steps, and it cannot move candidates. Move them in Keka.
- Keka has no Hire webhooks, so changes reach Metaintro on its next check, not right away.
- Metaintro matches existing candidates by exact email on the same job only.

## If something goes wrong

- **The credentials are rejected:** check that the client ID, client secret and API key all came from the same Keka account, that the key has not expired, and that the subdomain is right.
- **Access is refused:** check that the API key has the Hire privileges and scopes.
- **Too many requests:** Keka's minute limit was reached. Metaintro waits and tries again by itself.
- **A job is missing:** check the job exists in Keka Hire and that the API key can see Hire.

### Was this article helpful?

## Related Articles

- [Connect your ATS to MetaintroSend people who choose to share with you straight into your applicant tracking system, and see their stage in Metaintro.](/help/connect-your-ats-to-metaintro)

[Return to navigation](#main-navigation)