Before you start
You need a RecMan system administrator. Only system administrators can view or create API keys in RecMan.
RecMan's API is included with RecMan. It is free for 200 lookups a day, and RecMan charges for each lookup after that. Ask RecMan support for prices.
You will paste one thing into Metaintro: a RecMan API key.
Create the credential in RecMan
These steps follow RecMan's guide to obtaining an API key.
In RecMan, go to System settings > Database > API.
Select Create to make a new API key for Metaintro.
Add access for the key. Choose the modules it can use and the operations it can perform. Give it the candidate, job post, job application, log, candidate pipeline and corporation modules, with the get, insert and update operations.
Copy the API key.
RecMan's guide does not show the access screen in detail. Give the key only the modules and operations listed above, as RecMan recommends when you share a key with another company.
Connect in Metaintro
In Metaintro, go to Settings > Integrations.
Choose RecMan.
In API key, paste the key you created.
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 active RecMan job posts so you can map them.
Candidate: Metaintro looks for an existing candidate with the same email address. If there is none, it creates one in the job post's corporation, with their name, email and phone. The link to their proof card goes in the candidate's website field.
Application: the person is added as an application on the mapped job post, with the status Untreated. The application text says they were shared through Metaintro and links to their proof card and summary.
Résumé: uploaded to the candidate and linked to the application when the person has one.
Note: if the person already had an application on that job post, Metaintro adds the proof card as a comment in the candidate's log instead.
Metaintro checks the application in RecMan regularly to read its status. Hired and Declined are read as hired and not selected. While the application is still open, Metaintro also reads the candidate's pipeline category, such as an interview step.
Metaintro can also mark the application Hired or Declined, or move the candidate to the pipeline category whose name matches the step.
Limits
RecMan has no webhooks, so stage changes reach Metaintro only when it next checks, not right away.
Metaintro keeps its own use to about 200 lookups a day so it stays within RecMan's free allowance. Each person shared takes several lookups, so busy days can queue deliveries until the next day.
RecMan has no source field, so the application does not show Metaintro as its source. The application text and the proof card link show where it came from.
Metaintro takes hired and not selected only from the application status, not from pipeline category names.
Metaintro matches existing candidates by exact email only. A person with no email is always created as a new candidate.
If something goes wrong
The key is rejected: check that you copied the whole key and that it still exists under System settings > Database > API. Then connect again.
Access is refused: open the key in RecMan and add the modules and operations listed above.
Too many requests: the day's allowance is used up. Metaintro waits and tries again later by itself.
A job post cannot be used: RecMan needs a corporation to create a candidate. Check that the job post belongs to a corporation.
A job is missing from the list: only active job posts are listed. Check that the job post is active in RecMan.