Connecting Carerix to everything around it
Carerix has a full-fledged API — GraphQL alongside REST — that lets you connect accounting, time tracking, your website and Power BI. For large staffing firms with a back office such as AFAS or Easyflex, partner connectors like Solid Online Connect exist (price on request); for agencies below that, a focused integration via iPaaS or a custom build is usually a better fit, an indicative €1,500 to €15,000 one-off.
- Fixed monthly fee
- Fixed project price up front
- Microsoft and Google
- Response to your request within one business day
What can you connect Carerix to?
Almost anything with an API: your accounting (Exact Online, Moneybird, Yuki), time tracking and payroll, your website and your BI environment. Carerix offers a REST API and a GraphQL API for that, letting you pull exactly the data you need per integration. In practice, these are the four integrations agencies most often have built — you can see what such a flow looks like in our interactive Flow Lab, and what a custom build costs in What does an API integration cost?
Accounting — a placement in Carerix automatically becomes a (draft) invoice in Exact Online, Moneybird or Yuki. Hours and payroll — worked hours flow through to invoicing or the payroll package, without retyping. Website — vacancies from Carerix live on your (WordPress) site and applications straight back into the system, via the GraphQL API. Power BI — your pipeline, placements and margins live on a single screen; we wrote a separate page about that: recruitment dashboard in Power BI. All the integrations we build are on the integrations overview.
Three routes to connect Carerix.
Which route fits depends above all on your back office and your size. For back-office integrations, Carerix works with integration partner Solid Online; for focused integrations you build directly on the API.
| Option | Type | Indicative cost | Suitable for |
|---|---|---|---|
| Solid Online Connect | Partner connector | price on request (Solid Online, 2026) | Larger staffing and secondment firms with a back office such as AFAS, Easyflex or HelloFlex and an ongoing integration programme |
| Make / Zapier / Power Automate | iPaaS workflow | from around $9 p/m in licences (Make, 2026) | Focused flows with standard steps; Carerix has no ready-made app in these tools, so connecting goes via HTTP requests on the API |
| Custom build on the GraphQL API | Custom | indicative €1,500–€15,000 one-off (see What does an API integration cost?) | Agencies that want to connect one or more systems tightly, with custom fields, custom rules and clean error handling |
What synchronises — and what doesn't?
The common flow — placement to invoice — is covered by both partner connectors and custom builds. The difference lies in custom fields, your website and reporting data: there the standard route is limited or absent.
| Data | Off-the-shelf connector | Custom integration |
|---|---|---|
| Placements → invoices in your accounting | Yes | Yes |
| Hours and rates to payroll or invoicing | Limited — partner connectors cover the common back-office packages | Yes |
| Vacancies to your website, applications back | Limited — depending on your website builder or plugin | Yes — directly via the GraphQL API |
| Custom fields and labels | Limited — standard field mapping, custom fields require configuration | Yes |
| Pipeline and history data to Power BI | No | Yes — see recruitment dashboard in Power BI |
| History before the start date | No | Optional |
Three questions and you'll know the route.
Does your back office run on AFAS, Easyflex or HelloFlex?
Yes → then a partner connector such as Solid Online Connect is the well-trodden path; those combinations have often been made there already. No → on to question two.
Is it about a single focused flow with standard steps?
Yes → an iPaaS workflow on the Carerix API is quick to build and cheap to run — think of an alert on every new placement or a weekly export. No → on to question three.
Do you want custom fields, two directions or BI data?
Yes → a custom build on the GraphQL API gives you full control over field mapping, deduplication and error handling. No → stick with the simplest route that covers your process.
The rule of thumb: the closer you stay to the standard Carerix setup, the cheaper and more robust the integration — a custom build is there for the part that genuinely deviates from the standard.
Where Carerix integrations come unstuck in practice.
Wanting to connect everything at once
Accounting, hours, website and BI in one project makes the go-live slow and the source of an error impossible to find. Start with the flow that cuts the most manual work — usually placement to invoice — and build out from there.
Custom fields that land nowhere
Agencies set Carerix up with custom fields and labels, but an integration only carries what is explicitly mapped. Before the build, run through the fields you want to see back in invoices or reports, otherwise that data disappears silently.
Applications that vanish along the way
With a website integration, the application flow is the most fragile: a candidate who doesn't reach Carerix, you only notice once the vacancy is already closed. Test the whole funnel — form, API call, confirmation — with real test candidates before the go-live.
An integration with no owner
API clients expire, fields change and nobody looks at the logs. Arrange monitoring and a single owner — internal or at your integration partner — so a stalled sync is noticed within a day rather than at the month-end close.
What agencies ask us up front.
What does a Carerix integration cost?
A custom build on the Carerix API costs an indicative €1,500 to €15,000 one-off, depending on the number of systems, the directions and the business rules. A first focused integration — for example placement to invoice — usually sits at the lower end of that band. Partner connectors such as Solid Online Connect have a price on request. We work with a fixed project price up front.
How long does it take to build a Carerix integration?
A focused integration with standard steps is often up within one to a few weeks, including testing with real data. The lead time depends above all on how many custom fields and exceptions your process has and how quickly test data and API access are arranged.
What is the difference between the Carerix REST API and GraphQL API?
Carerix offers both. The GraphQL API is the newer layer: per integration you request exactly the fields you need, in a single request on a single endpoint. For new integrations — especially vacancies on your website and applications back into the system — GraphQL is the logical choice; existing REST integrations keep working.
Who manages and monitors the integration?
You agree that up front. We actively monitor the integrations we build, as part of a fixed monthly fee: we see it when a sync stalls or an API client expires, and fix it before it touches your administration.
Do we have to switch ATS first?
No. We build around Carerix; the system has a full-fledged API, so switching is not necessary for an integration. If you are about to switch anyway, or to reconfigure, that is precisely a good moment to design the integrations in at the same time.
Ready to let Carerix really flow through?
Book an intro call — or start with the free Operations Scan and see where the hours leak away at your agency.