Connect Djinni to RolePark

Before you start

• An employer account on Djinni with access to the API. Open https://djinni.co/home/profile/: if your company has API access, you will see the “ATS” tab. If it is missing, write to Djinni support at magic@djinni.co.
• A company admin account in RolePark. Only a company admin connects Djinni; recruiters then publish vacancies.
• One Djinni API key per company. It is not tied to a particular person, so it keeps working when your team changes.

Step 1. Create an API key in Djinni

1. Open https://djinni.co/home/integrations/ (the “ATS” tab in your Djinni profile).
2. Click “Створити ключ” / “Create key” and copy the key.
3. Turn on “Увімкнути поле ATS Job ID у вакансіях” (ATS Job ID field in vacancies). Djinni then returns the RolePark vacancy id with every application, so each application lands on the right vacancy.

The red “Delete” button next to the key removes it. After that RolePark stops publishing until you paste a new key.

https://djinni.co/home/integrations/ ↗

Step 2. Paste the key into RolePark

1. In RolePark open Settings → Job boards → Djinni.
2. Paste the key into “Djinni API key” and click “Connect”. RolePark checks the key with Djinni right away.
3. Choose the defaults Djinni requires and RolePark has no equivalent for: “Recruiter on Djinni” (an e-mail from your Djinni recruiters), “Domain” and “Category”. Click “Save defaults”.

The key is shown only as its last four characters after saving. “Verify key” repeats the check at any time; “Replace key” swaps it without losing the webhook settings.

Step 3. Webhook for applications

RolePark creates the webhook in Djinni automatically through the Djinni API when the key is verified. You do not need to do anything; the Djinni card in RolePark says “RolePark created the webhook in Djinni automatically”.

If you prefer to add the webhook by hand, open Djinni → ATS → Webhooks and enter:

Each company has its own unguessable address and token. RolePark checks the token on every request. “New address and token” in the card replaces both at once.

Publishing a vacancy

1. Open the vacancy in RolePark → “Postings” tab → the “Djinni” panel.
2. If something Djinni requires is missing, the panel lists it. To publish, Djinni requires a salary range (salary from and to); a draft can go without it. RolePark sends the vacancy range automatically only when it is in US dollars per month; otherwise enter the range for Djinni in “Djinni fields for this vacancy”.
3. Click “Publish on Djinni”: RolePark creates the posting on Djinni and publishes it in one step. “Save as a Djinni draft” creates an inactive draft that candidates do not see; publish it later with “Publish on Djinni”.
4. Djinni moderates new postings. While it reviews, the status is “Under Djinni moderation”.

Statuses in RolePark

• In queue — the request is on its way to Djinni.
• Draft — the posting exists on Djinni but candidates do not see it.
• Under Djinni moderation — Djinni is reviewing the posting.
• Published — candidates see the posting on Djinni.
• Paused on Djinni — the vacancy is on hold; the posting is inactive on Djinni and comes back when the vacancy opens again.
• Error — Djinni rejected the request; the reason is shown next to the status and in the sync journal.
• Removed — the posting is archived on Djinni.

• When you edit the vacancy in RolePark, the posting on Djinni is updated.
• When you put the vacancy on hold, RolePark pauses the posting on Djinni and reactivates it when the vacancy is open again. When you close, unpublish or delete the vacancy, RolePark removes it from Djinni.
• If Djinni is temporarily unavailable, RolePark retries with growing pauses and respects the Djinni limit of 100 requests per minute.

Where applications appear

• Djinni sends each new application to RolePark through the webhook as soon as it arrives. Every 15 minutes RolePark also checks the applications of each published vacancy, so nothing is lost if a webhook did not arrive.
• They appear in the vacancy → “Inbox” tab with the “Djinni” badge and a link to the candidate’s Djinni profile. Accept or decline them as usual.
• If the same person also arrives through a Djinni e-mail notification, RolePark recognises them by the Djinni profile link and does not create a duplicate.

What data is transferred

RolePark → Djinni

• vacancy title, description, required and nice-to-have skills, location and work format;
• salary range (shown publicly only if it is public in RolePark), domain, category and the Djinni recruiter;
• the RolePark vacancy id (as ATS Job ID).

Djinni → RolePark

• name and contacts, if the candidate shared them with you; Djinni profile link, CV link, cover letter and time of the application.
• RolePark does not import gender, mobilization deferment, photo, messengers or quiz answers: you see them in the profile on Djinni.

• The Djinni API key is stored encrypted (AES-256-GCM) and is never shown again after saving or written to logs.
• Disconnecting deletes the key and the webhook. Postings already on Djinni stay there until you remove them.

Privacy ↗

Support

Questions about RolePark: help@rolepark.com

Questions about API access on Djinni: magic@djinni.co.