Connect Eploy to Metaintro

Before you start

You need an Eploy user who can manage users and who has the Configure API Keys permission. Your Eploy system must have the API turned on.

Eploy's API package sets how many calls you can make each day. The default is 1,000 a day, shared by every integration in your system. Your Eploy Account Manager can tell you about larger packages.

Ask Metaintro support for the IP addresses Metaintro calls from. You will need them for the API user.

You will paste three things into Metaintro: your system name, the API key's client ID and its client secret.

Create the credential in Eploy

These steps follow Eploy's guides to setting up an API user and setting up an API key.

First, create the API user:

1. Go to Admin > Users, Roles & Permissions > Users.

2. Click New > Standard and create a user just for Metaintro, such as "Metaintro API User".

3. Give the user exactly one role. The role decides what the API can see.

4. Save, then in Restricted IP Access, add Metaintro's IP addresses.

Then create the API key:

1. Go to Admin > System/Security Settings > API Keys.

2. Click New > REST API.

3. Enter a Title, such as "Metaintro", and choose the API user as Run As User.

4. Click Save.

5. Copy the Client ID. Click Show next to the client secret and copy it now. You cannot see it again after you leave the page.

6. Under API Permissions, click Add and give the key View and Insert permission for vacancies, candidates, applications and notes.

7. Click Save.

Connect in Metaintro

1. In Metaintro, go to Settings > Integrations.

2. Choose Eploy.

3. In System name, enter the part before .eploy.net in your Eploy address.

4. In API key client ID, paste the client ID.

5. In Client secret, paste the client secret.

6. 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 the vacancies your API user can see so you can map them.

• Candidate: Metaintro looks for an existing candidate with the same email address. If there is none, it creates one with their name, email and mobile number, the source Metaintro, and their proof card link as the website.

• Résumé: uploaded as the candidate's CV when the person has one.

• Application: the candidate is applied to the mapped vacancy with the source Metaintro.

• Note: a note called "Shared through Metaintro" with the link to their proof card.

Metaintro checks each application in Eploy regularly and reads its stage and status. Placements, rejections and withdrawals are read from them. Metaintro does not move applications in Eploy; you do that in Eploy.

Limits

• Every call counts against your daily Eploy allowance, which your other integrations share. Metaintro paces itself to about 1,000 calls a day, so busy days can queue deliveries until the next day.

• Eploy has no stage webhooks, so changes reach Metaintro on its next check, not right away.

• Metaintro matches existing candidates by exact email only.

If something goes wrong

• The client ID or secret is rejected: check you copied both from the same key. If you lost the secret, generate a new client ID and secret on the key and connect again.

• Access is refused: check that the API user's Restricted IP Access includes Metaintro's IP addresses, that the user has one role, and that the key has the permissions above.

• Too many requests: today's Eploy allowance is used up. Metaintro waits and tries again later by itself. Ask your Eploy Account Manager if you need a bigger package.

• A vacancy is missing: the API user's role cannot see it. Check the role's access in Eploy.