Skip to main content
Our Oleeo integration connects vacancies, candidates, and applications to Alex, keeping both platforms in sync throughout the interview process.

​
How the Integration Works

​
Automated Interview Creation

When a vacancy is posted in Oleeo, an interview can be automatically generated in Alex. The vacancy’s title and description are used to create the interview.

​
Automated Interview Invitations

When an application in Oleeo reaches the stage your team gates interviews on, Alex automatically invites the candidate to complete an interview. You choose which Oleeo status triggers the invitation — Alex listens for that status change in real time.

​
Screening on Application Answers

Alex can screen applicants on the answers they gave on your Oleeo application form — work authorization, sponsorship, GPA, or any other question on the form — before deciding whether to invite them to an interview. Your questions appear by name when you build the workflow, so there are no field ids to look up, and answers with a fixed set of choices are offered as a dropdown of your own values. Questions collected for equal-opportunity monitoring — ethnicity, gender, sexual orientation, disability, and similar — are deliberately not available to screen on, even though Alex can see them on the form. An application’s current Oleeo status is also available, which is the usual way to skip applicants your team has already closed out.

​
Interview Results in Oleeo

After a candidate completes an interview, Alex adds a comment to the application containing the interview summary and a link to the full interview report. The comment is composed per workflow in Alex. Advancing or rejecting the application in Oleeo based on the interview outcome is configured separately, under “Settings” → “ATS Sync” → “Interview Sync”, where you map each Alex outcome to one of your own Oleeo statuses.

​
What We Need From Your Team

Alex connects to your Oleeo system with a dedicated API service account. Your Oleeo administrator (or Oleeo support contact) will need to provide:
  1. Your system identifier — the subdomain in your Oleeo URLs (the yourcompany in yourcompany.tal.net). If you have a config/test system (yourcompany-config.tal.net), we recommend connecting Alex to it first to validate the integration before going live.
  2. An API service account — a username and password provisioned for API access with the recruiter API scope (ats_recruiter).
  3. Service account permissions — the account should be able to:
    • Read vacancies, candidates, and applications (including CVs)
    • Read application form answers and the option lists behind them
    • Create candidates and applications
    • Move applications between statuses and add application comments
    • Create notification topics and subscriptions
Once you have these, enter them in “Settings” → “Integrations” in the Alex web app, or share them securely with your Alex onboarding contact.

​
Real-Time Updates

Alex registers its own webhook subscriptions in your Oleeo system over the API — no webhook configuration is needed on your side. Subscriptions are signed and verified on every delivery, and Alex renews them automatically before they expire.

​
Fair Use

Oleeo’s API policy asks integrations to make one request at a time per account. Alex enforces this automatically — all requests to your Oleeo system are serialized and rate-limited, so the integration never impacts your Oleeo system’s performance.