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.
Sign in to Keka as a Global admin.
Go to Global admin settings > Integrations & Automations > API access > API key.
Generate the client ID and client secret. Copy both.
Generate an API key. Select the privileges and scopes for Hire.
Optionally, turn on Set expiry and choose a date. The connection stops working on that date.
Copy the API key.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose Keka Hire.
In Keka company subdomain, enter the part before .keka.com in your Keka address.
In Client ID, paste the client ID.
In Client secret, paste the client secret.
In API key, paste the API key.
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.