Skip to main content

Integration status

Each connection below shows its state, the date that state was recorded, what it is waiting on and the release it is planned for. If a connection is not live, its row says so.

At a glance

  • Live3 integrations
  • Simulated8 integrations
  • Export only1 integration
  • Planned7 integrations

Each entry is checked against its provider again by November 30, 2026.

What each state means

Live
Works today in the product.
Simulated
Works in the demo with simulated traffic. Nothing is sent to the provider.
Export only
The product produces a file that you upload to the provider yourself.
Partner approval pending
An application has been filed with the provider, on the date shown, and waits on its partner approval.
OAuth verification pending
A verification request has been filed with the provider, on the date shown, and waits on its review of the app’s permissions.
Planned
On the roadmap. Not built yet.

Careers pages

IntegrationStateDetails
Careers pageLive

Bilingual careers pages hosted for each customer, with the apply flow, the privacy notice candidates read first and the “Report this posting” control.

Application intake

IntegrationStateDetails
Email intake addressSimulated

Simulated since October 9, 2026. Each job’s intake address works in the demo through the sample-email tool, and the parsing is the same code that will read real mail. Receiving mail sent from outside starts with the pilot release, once the inbound provider and its storage region are confirmed.

  • Planned for release 0.2, target Q1 2027
Applications APILive

Live since October 9, 2026. A customer’s own site, applicant tracking system or job board sends applications with an API key from Settings › API. Each one states its legal basis, and goes through the same reading, redaction and matching as any other application.

API syncLive

Live since October 9, 2026. Reads new applications every 15, 30 or 60 minutes from another system’s JSON API that holds applications candidates made or agreed to share. JSON APIs only: web pages and social networks are refused. The demo includes a simulated applicant tracking system served by the product itself.

Job boards

IntegrationStateDetails
IndeedSimulated

Simulated since October 9, 2026. The Indeed developer agreement has not been requested yet; Indeed’s review usually takes about six weeks from the request, and its date will appear here once it is made. Publishing returns a simulated receipt, and applications in the demo come from a local simulator signed the way Indeed signs them, so the signature check is the real one.

  • Planned for release 1.0, target Q4 2027
Job BankExport only

Export only since October 9, 2026. Job Bank has no posting API for employers. Download the export, tagged with the job’s NOC 2021 code, and post it from your Job Bank employer account. Job Match invitations sent from Job Bank are logged here by hand.

  • Planned for release 1.x, not scheduled yet
JobillicoPlanned

Planned since October 9, 2026. Posting to Jobillico, for Québec, is planned for release 1.0. Nothing is sent to Jobillico today.

  • Planned for release 1.0, target Q4 2027
LinkedIn Job Posting APIPlanned

Planned since October 9, 2026. Posting jobs to LinkedIn needs approval in LinkedIn’s Talent Solutions partner program, which looks for existing customers. The application has not been filed yet; once it is, its date will appear here and the state will change to partner approval pending.

  • Planned for release 2.0, not scheduled yet

Applicant tracking systems

IntegrationStateDetails
LinkedIn Recruiter System ConnectPlanned

Planned since October 9, 2026. Recruiter System Connect comes after the Job Posting API integration. It needs LinkedIn’s partner approval, the five integration modules and a module that deletes member data on request; no application has been filed yet. Until then, candidates can import their own LinkedIn PDF export from their portal.

  • Planned for release 2.0, not scheduled yet
  • Member-data deletion module: to be built before the integration goes live
BullhornSimulated

Simulated since October 9, 2026. Payload preview only: the page shows the candidate and submission records a sync would send to Bullhorn, and nothing is sent. Live sync needs API access through Bullhorn’s partner program and is planned for release 1.0.

  • Planned for release 1.0, target Q4 2027
ManatalSimulated

Simulated since October 9, 2026. Payload preview only: the page shows the candidate record a sync would send to Manatal, and nothing is sent. The field names still have to be checked against Manatal’s API before live sync in release 1.0.

  • Planned for release 1.0, target Q4 2027
RecruiterflowSimulated

Simulated since October 9, 2026. Payload preview only: the page shows the candidate record a sync would send to Recruiterflow, and nothing is sent. The field names still have to be checked against Recruiterflow’s API before live sync in release 1.0.

  • Planned for release 1.0, target Q4 2027

Calendars

IntegrationStateDetails
Google CalendarPlanned

Planned since October 9, 2026. Reading free and busy times needs Google to verify the app’s calendar permission, and that request has not been made yet. Until then, recruiters propose times by hand and candidates get a calendar file (ICS) for the slot they pick.

  • Planned for release 1.0, target Q4 2027
Microsoft Outlook calendarPlanned

Planned since October 9, 2026. Finding meeting times in Microsoft 365 needs Microsoft’s publisher verification, not requested yet, and each customer administrator’s consent. Until then, recruiters propose times by hand and candidates get a calendar file (ICS) for the slot they pick.

  • Planned for release 1.0, target Q4 2027

Email and text messages

IntegrationStateDetails
Email deliverySimulated

Simulated since October 9, 2026. Approved messages go to the outbox: each one is stored exactly as it would be sent, and its delivery, bounces and unsubscribes are simulated. Nothing leaves the system. Amazon SES in Canada (Central) is the planned transport.

  • Planned for release 0.2, target Q1 2027
Text messagesSimulated

Simulated since October 9, 2026. Text messages go to the outbox, where delivery and STOP replies are simulated; nothing is sent. Sending needs a verified Canadian toll-free number, which typically takes two to three weeks.

  • Planned for release 0.2, target Q1 2027

Platform services

IntegrationStateDetails
Card paymentsPlanned

Planned since October 9, 2026. Payments pending: card billing is not set up, and subscriptions are invoiced directly until it is.

  • Planned for release 1.0, target Q4 2027
Interview transcriptionSimulated

Simulated since October 9, 2026. The demo uses prepared transcripts. Recordings are to be transcribed by Amazon Transcribe in Canada (Central) from release 1.0; Deepgram is a disclosed alternative.

  • Planned for release 1.0, target Q4 2027
MCP server (read-only)Planned

Planned since October 9, 2026. A read-only Model Context Protocol server, so customers’ own assistants can look up jobs and pipeline status, is planned after release 1.0.

  • Planned for release 1.x, not scheduled yet

For developers

A customer’s own site, applicant tracking system or job board can send applications to TalentInitiator through the Applications API, with an API key per organization. The API is described in OpenAPI 3.1.

Open the OpenAPI description

The LinkedIn partner path

LinkedIn shares member data with recruiting software only through its Talent Solutions partner program. This is the order we follow, and the only way we connect to LinkedIn.
  1. Job Posting API

    Publish jobs to LinkedIn from the product. The partner program looks for existing customers, so the application is filed once there are customers to show.

    Planned
  2. LinkedIn Recruiter System Connect

    Sync candidates and InMail history from each customer’s own Recruiter seats, with the customer’s authorization and LinkedIn’s member-data deletion module.

    Planned

Until then, candidates can upload their own LinkedIn profile export from their portal, and recruiters keep using their Recruiter seats as they do today.

No browser extensions, no logins on a recruiter’s behalf, no copying of profiles.

Read our responsible sourcing policy 

Need an integration that is not listed?

Tell us which system you use and how you use it today. We record every request and say plainly when we can and cannot build it.