INTEGRATIONS · EXPERTINI ATS

Programmatic Job Ads

Distribute your jobs to 250+ Expertini country sites through one campaign.

2 min read · Updated July 2026 · Expertini Editorial

Reach is the first bottleneck in every hiring pipeline: a job nobody sees produces no candidates, however good the process behind it. Programmatic Job Ads turns one published Expertini ATS job into a campaign across more than 250 Expertini country job sites — one setup, one dashboard, distribution across an entire network that would take weeks to cover posting site by site.

The gap this closes is the manual multi-posting grind and the aggregator fees that usually replace it. Traditional job distribution means either an afternoon of repeated form-filling per role or a separate programmatic vendor with its own contract and margin. Here, distribution is a native feature of the ATS you already subscribe to: pick jobs, launch the campaign, and every application funnels back into the same hiring pipeline with its source recorded. Pair it with bulk job posting and a full slate of vacancies can go network-wide in one sitting.

▶ Watch the 30-second overview — no sign-up needed

01One campaign, 250+ destinations

Each Expertini country site is a live job board with its own local audience. A programmatic campaign places your listing across the network without you creating accounts, reformatting descriptions, or tracking dozens of logins. The job you wrote once is the job everywhere — updated centrally, closed centrally.

That matters most for roles with wide or flexible geography: remote positions, multi-country expansion hiring, and agencies filling roles for clients across borders.

02Applications that come home

Distribution is only half the job; the other half is not losing what comes back. Every application generated by the network arrives in your ATS pipeline like any direct applicant — same stages, same scoring, same scheduling. Source tracking shows which countries and sites produce candidates, so the next campaign is better informed than the last.

03Native beats bolted-on

Because distribution, careers site, and pipeline are one product, there is no feed to maintain, no XML integration to break, and no third-party programmatic contract. It is included in your subscription — see pricing — and it stacks with the automatic Google for Jobs submission every published job already gets.

Engineering notes

Platform architecture & operations

A1Connection architecture

The connection model for this integration is stated honestly on its card: where a public API exists it is used with your own account and consent, and where a vendor requires a partner agreement the page says so instead of showing a Connect button that cannot work.

Once available, credentials follow the platform standard: encrypted at rest, presence-flag display, immediate removal on disconnect.

A2Write semantics and data flow

Every data movement is an explicit action with a logged result. Writes happen on your click — or automatically only where you enabled a rule (auto-push on hire is off by default, per-provider). Reads — imports of people, accounts, or files — run when you press Import, deduplicate against what you already have (clients by name, people by email), skip rather than overwrite, and report created-versus-skipped honestly, which is why re-running any import is safe by design.

Each action writes a row to the app-activity journal (ats_app_activity): what ran, when, for which record, and the outcome — including the vendor's own error text verbatim when something fails. Usage reporting inside the ATS aggregates that same journal, so integration reporting and integration reality cannot diverge.

Anything that leaves the request path — notification fan-out, webhook delivery, activity journalling, mail — runs in fire-and-forget background threads. A slow external endpoint can never make the interface hang, and a failed side effect is logged rather than silently retried into inconsistency.

A3Operational considerations

Connections are organisation-level and gated to owner and admin roles; recruiters use the features a connection powers but cannot connect, disconnect, or reconfigure. Disconnecting removes stored credentials immediately and stops the dependent features visibly, not silently. Data already imported stays yours and editable.

Imported people arrive marked as imported with conservative privacy defaults — no consent is assumed for anyone who never filled in your application form, and retention defaults apply. Everything written is yours to take: CSV exports and the Data Export app cover the same stores the product itself reads. The exit is as open as the entrance — by design, not concession.

A4Placement in the integration topology

This integration is live in the registry today. One connection per provider unlocks every feature it powers, and the topology grid below shows the neighbouring connectors in the same capability area — statuses come from the same registry that drives the in-app hub, so this page can never claim more than the product does. For anything the catalogue does not cover, Webhooks and Zapier are the generic, documented escape hatch.

Dependency map

Connection typestated per-vendor on the card

Secrets at restencrypted; UI shows presence flags, never values

Action journalats_app_activity — one row per action, vendor errors verbatim

Auto-push rulesoff by default, per-provider, every run logged

Registry statuslive

Interface blueprint

Structural schematic of the surface — panels, hierarchy, and interaction affordances. A contract, not a screenshot.

Connection card

● connected — presence flag

scopes: minimum required disconnect

Actions

push — explicit clickimport — deduplicated

Activity journal

Fig. 1 — Programmatic Job Ads: structural interface schematic. Panels and states are the contract; data shown is placeholder.

Interaction flow — states, validations, feedback

Every state below is enforced server-side; the interface reports it, it doesn't decide it.

Connectowner/admin clicks Connect on the Connectors page

Vendor consentthe vendor's own screen lists the exact scopes

Token exchangeserver-side callback; secrets never touch the browser

Connectedencrypted store; card flips with presence flag

Explicit actionspush / import / schedule — each one journalled

Consent denied → the vendor's error code surfaces in a toast, namedPlatform keys missing → honest setup pointer, not a silent bounceToken expired → automatic refresh at the chokepointRefresh rejected → visible reconnect prompt, features never break silentlyPlan below minimum → lock card names the exact plan

Fig. 2 — interaction flow: navy = states, gold = server-enforced gates, green = confirmed outcomes; tags list the edge cases and their feedback.

Frequently asked questions

How is this different from posting to job boards manually?⌄

One campaign replaces hundreds of individual postings. You set it up once in the ATS, and the network placement, updates, and closure are handled centrally instead of login by login.

Where do applications go?⌄

Straight into your ATS pipeline, with the source recorded. There is no separate inbox to check — network applicants are screened, scored, and scheduled exactly like direct ones.

Do I need a separate programmatic advertising vendor?⌄

No. Distribution across the Expertini network is a native feature of the ATS subscription — no additional contract, integration project, or vendor margin.

Which roles benefit most?⌄

Roles with broad geography — remote work, multi-country hiring, agency work for international clients — and any role where the local applicant pool has been too thin.

At a glance

250+ Expertini country sites from one campaign
No per-board accounts or repeated form-filling
Applications return to one pipeline with source tracking
Central updates and closure across the network
Stacks with automatic Google for Jobs submission
Included in the subscription, no distribution vendor

See programmatic job ads on your own hiring.

Bring a real job description to a 30-minute demo — free trial included.

Book a demo