What this API does
A public, machine-to-machine HTTP API for accountant-software vendors who submit salary data on behalf of their clients. You authenticate with an API key, classify rows against the job-family catalog, and push salary batches into every survey the customer is eligible for — without touching the portal UI.
- POST/v1/auth/tokenExchange an API key for a 15-minute JWT.
- GET/v1/job-family-catalogFetch the active job-family hierarchy.
- POST/v1/salary-rowsMerge rows into every eligible survey (default, safe).
- POST/v1/salary-rows/replaceReplace the participant's rows (destructive).
- GET/v1/healthLiveness probe.
Quick start
Three calls take you from an API key to imported salary rows. Full walkthrough in the Getting started guide.
Exchange your key for a token
curl -X POST https://api.fontes.ee/v1/auth/token \
-H "X-Api-Key: fpk_live_..."
Fetch the job-family catalog
curl https://api.fontes.ee/v1/job-family-catalog \
-H "Authorization: Bearer <token>"
Submit a salary-row batch (merge)
curl -X POST https://api.fontes.ee/v1/salary-rows \
-H "Authorization: Bearer <token>" \
-H "Idempotency-Key: $(uuidgen)" \
-H "Content-Type: application/json" \
-d '{"customerRegNo":"12345678","rows":[
{"jobFamilyCode":"JF001","personalCode":"38001010000","grossSalary":2500.00}]}'
Need a key? API keys are issued by Fontes support. Email api-support@fontes.ee with your integration name and the responsible organisation.
Explore the docs
Interactive reference with “Try It”, plus narrative guides for the topics that trip integrators up.
API reference →
Interactive Scalar UI with every endpoint, schema, and a live “Try It” console.
Getting started →
The complete four-step flow from API key to imported rows.
Authentication →
Token lifetimes, the 401-then-reissue pattern, and key rotation.
Merge vs replace →
Side-by-side comparison so you pick the right endpoint deliberately.
Idempotency & retries →
How Idempotency-Key makes retries safe, and what reuse returns.
Errors →
RFC 9457 ProblemDetails responses and the full error-code reference.
OpenAPI document →
The raw OpenAPI 3.1 spec — feed it to your client generator.
Changelog →
What changed in v1, and how breaking changes are versioned.