Connecting OTYS to the rest of your agency
OTYS is emphatically API-first: through OTYS Web Services (OWS) an integration can do virtually everything a user can in OTYS Go! (OTYS, 2024). For common links such as Exact Online and Easyflex there are partner connectors; for everything else you build on the API. Integration partners quote roughly €1,000–€10,000+ per integration (Brixxs, 2026); our own custom band is €1,500–€15,000.
- Fixed monthly fee
- Fixed project price up front
- Microsoft and Google
- Response to your request within one business day
What can you connect to OTYS?
In practice, almost anything with an API, along four fixed groups: your website (vacancies and applications), your accounting and invoicing, your hours and payroll, and your reporting in Power BI. OTYS provides two entry points for this: the Web API for websites and OWS for the back-office data, both with partner documentation (OTYS, 2024). You can see what such a flow looks like in our interactive Flow-Lab; the cost breakdown is in What does an API integration cost?.
You will find all the systems we connect on the integrations page. If you work with a different ATS, take a look at connecting Carerix or connecting Recruitee to AFAS — the pattern is the same, the details differ per system.
Four routes, side by side.
| Option | Type | Indicative cost | Suitable for |
|---|---|---|---|
| Solid Online Connector | Partner connector | Subscription, price on request (OTYS, 2026) | Placements and relations into Exact Online; hours into packages such as Easyflex |
| Integration partner (e.g. Brixxs) | Outsourced API integration | Indicatively €1,000–€10,000+ per integration (Brixxs, 2026) | Integrations on the OTYS API, built and managed by an external party |
| Make / Zapier / Power Automate | iPaaS workflow | From around $9/mo (Make, 2026) to $19.99/mo (Zapier, 2026) | Small flows via webhooks and HTTP steps, at low volumes |
| Custom build on OWS | Custom build | Indicatively €1,500–€15,000 one-off (see What does an API integration cost?) | Placement-to-invoice with your own business rules and a data layer for Power BI |
What syncs — and what doesn't.
With a partner connector, the common data comes across: relations, placements and invoicing details towards your accounting, and hours towards supported packages. Everything beyond that — custom fields, reporting data, history — is API work. Because OWS exposes virtually the entire OTYS database (OTYS, 2024), the question is rarely whether something is possible, but by which route.
| Data | Standard connector | Custom integration |
|---|---|---|
| Relations and debtors into accounting | Yes | Yes |
| Placements as the basis for invoices | Yes | Yes |
| Vacancies and applications on your own website | Limited — via the OTYS website module; a custom site needs the Web API | Yes |
| Hours into payroll | Limited — only for supported packages such as Easyflex | Yes |
| KPIs in Power BI (fee pipeline, time-to-fill) | No — there is no standard Power BI connector | Yes |
| History from before the start date | No | Optional |
Three questions that decide the choice.
Is there a partner connector for your link?
Yes → take it: managed connectors exist for Exact Online and Easyflex, among others. No → then OWS is the route, with a custom build or an integration partner.
Is there custom logic in the flow — margins, fee splits, status rules?
Yes → custom build, because a standard connector syncs fields and applies no business rules. No → a connector or a small iPaaS flow will do.
Do you want reporting across multiple systems?
Yes → build a data layer that brings OTYS and your accounting together and let Power BI run on top of it. No → the reporting in OTYS itself gets you a long way.
The rule of thumb: a connector where one exists, a custom build on OWS as soon as custom logic or reporting comes into play — and never two routes writing the same data.
Where this project runs aground in practice.
Trying to solve everything via the website module
The Web API is meant for vacancies and applications on your site; back-office flows belong on OWS. Anyone using the website entry point for both builds an integration that breaks the moment the site changes.
An API user with no owner
The permissions of the OWS user determine what the integration can do. Change a role or a login, and the integration fails silently. Record who manages the API access and have the integration actively monitored.
Power BI directly on the live API
Every refresh then pulls heavy queries across your OTYS environment, causing slowness and hitting API limits. Put an intermediate layer with its own data storage between OTYS and your dashboard.
Connecting the chain halfway
Pushing placements through to invoicing without also syncing relations and debtors produces matching errors — and therefore manual work after all. Design the whole chain, not one link.
What agencies ask us up front.
What does an OTYS integration cost?
Partner connectors work on a subscription with pricing on request. Integration partners quote roughly €1,000 to well over €10,000 for an API integration, depending on the complexity. Our own band for custom builds is roughly €1,500 to €15,000, with a fixed project price up front — a first working integration usually sits at the lower end.
How long does an OTYS integration take?
An existing partner connector is typically live within a few weeks, including setup and testing. A custom build on OWS usually takes a few weeks to a couple of months, depending on the number of links and the test steps with your back office.
What if a connector stops or does not carry all fields?
There is always a fallback: OWS exposes virtually the entire OTYS database, so a custom integration can replace or complement any connector. What matters is that one party keeps the overview, so that two routes are not writing the same data side by side.
Who manages and monitors the integrations?
This should be assigned to someone, otherwise an integration fails silently — for example through a changed authorisation or an API update. We include monitoring and maintenance in a fixed monthly fee: changes on the OTYS side or in the connected package are tracked and errors are flagged before the back office notices them.
Do we need to move away from OTYS to do this?
No, quite the opposite. OTYS is built to be integrated: virtually everything a user can do in OTYS Go! an integration via OWS can do too. Switching your ATS is almost never necessary for integrations; we build around your current setup.
OTYS as the source, the rest follows automatically.
Book an intro call — or start with the free Operations Scan and see which link costs your agency the most time.