The same operations
What you do on screen, you do through a call: sites, content, images, themes, menus, redirects, publishing, Search Console. The documentation lists every operation, one by one.
Developers
Joornal is driven through its API
Everything the back-office does can be done through the API: create a site, import content, publish, read Search Console data. With your own tools, inside your own pipelines, under the same permissions as your users.
The same thing as the interface, without the interface
This API is not a grudging subset. It is the same application, seen from the other end.
The same permissions
A token only reaches its holder’s scope: their customer, their projects, their sites. A resource outside it answers 403. There is no separate “API account” with its own rules to keep in sync.
No session, no cookie
One X-API-TOKEN header per call, verified every time. Nothing to open, nothing to renew, nothing to keep in a browser.
Errors that look alike
A single error contract across the whole API: a stable machine code, a readable message, and field-by-field detail when validation fails. You write the error handling once.
What you drive
The uses that come up most often with agencies and multi-brand groups.
Feed it from your own systems
Bulk content import, idempotent: replaying the same call creates no duplicate, and you decide whether it leaves existing items alone or updates them. You can backdate, schedule a publication, attach categories and signatories, and push images in the same move.
Take over an existing site
Migration from WordPress or from an export, then go-live: theme, domain, redirects, sitemap. The estate is created and configured through calls, not through tickets.
Publish at the right moment
Trigger a publication, reschedule a queue of articles, follow the progress. Long operations return a task id you poll until it is done.
Pull the data back
Search Console performance per article, indexing state URL by URL, crawler traffic statistics, leads from the contact form. To feed your own dashboards instead of retyping them.
What you can count on
An API worth wiring in is one whose rules you know up front. Ours are written in the documentation, not in a contract you have to ask for.
One year after deprecation
A field or an operation on its way out is marked in the specification first, with its replacement and the date of the mark. It keeps being served for at least one year from that date. You always have a full year to move.
A specification that does not lie
The OpenAPI specification is public, and our continuous integration refuses any change to the API that does not come with its documentation. The docs cannot fall behind in silence: they show the date they were last reviewed.
Limits you are told about
Every response carries the budget you have left. You never have to discover a limit by hitting it, and you can slow down before it stops you.
An unknown filter is refused
A misspelled or retired parameter produces an error, never a result that merely looks right. That is the kind of detail you only notice the day it has cost you a week.
Take back control of your visibility
Book a demo on your own site and see how a structured, data-driven media property gets built.