Measure your job ads with Frantz
Send Frantz the job ads you publish, put the Frantz script on each ad's page, and read how many people saw the ads, read the job ad and clicked apply, per channel. Partners in the pilot can also order campaigns for their job ads.
How it works
- Sign inGet a token with the client id and secret Frantz gives you.
- Send a job advertYour reference and the ad's address. You get a ConnectID and a script.
- Add the scriptPut it at the end of
<head>on the job ad's page. - Read statisticsOnce a day, per channel, for the job ad's whole life.
Get started
The four steps with examples in cURL, C#, JavaScript and Python.
Read the guideSign-in and scopes
Clients, secrets, tokens that last an hour, and what each scope lets you do.
Read the guideJob adverts and ConnectID
Your reference, Frantz' ConnectID, safe retries, changes, the script and audiences.
Read the guideStatistics
What each number means, when it is updated, and how to store it.
Read the guideCampaigns
A preview: advertisers, quotes, drafts and ordering, and following a campaign while it runs.
Read the guideErrors
Status codes, Problem Details, and what to retry.
Read the guideMoving from v1
Every v1 call and field, and what it is in v2. Your job adverts come with you.
Read the guideEnvironments
| Environment | Address | Use it for |
|---|---|---|
| Test | https://apitest.frantz.no | Building and testing your integration. Nothing here is advertised. |
| Production | https://api.frantz.no | Your real job ads. |
Frantz gives you a client for each environment. A client from one environment does not work in the other.
What v2 has today
Sign-in, job adverts, audiences, and statistics for a job advert, for its whole life, a period or per day, are ready to use.
Campaigns are a preview for partners in a pilot with Frantz. Advertisers, media products, places, quotes, campaign drafts with their material, ordering, cancelling, pausing, starting again and stopping, and the campaigns' status, statistics and budget, are ready: see Campaigns. Add-ons and media packages from the agreements with Frantz cannot be chosen through the API yet.
The reference shows the whole contract for v2, so it also has what is still coming:
- Impressions and clicks for a period and per day. Until then, they are
nullwhen you sendfromandto, and indays.
Conventions
- Requests and responses are JSON, with field names in camelCase. Only
POST /api/v2/auth/tokentakes a form. - The HTTP status tells the outcome. Errors have a Problem Details body.
- Amounts are in Norwegian kroner (
NOK), excluding VAT: what the advertiser pays. - Dates are
YYYY-MM-DDand mean calendar days in Norway. Points in time are UTC, such as2026-10-19T08:15:02Z. - A field without a value can be
nullor left out of a response. Treat the two the same. - New endpoints, new optional fields and new values in lists can appear in v2 without notice. Ignore what you do not know. Changes that would break your integration come in a new version.
Still on version 1?
Version 1 keeps working. Moving from v1 shows what every call and field is in v2, and the version 1 rules are still here while you move.