REST API

Everything you do in Tesria, from opening a page to adding a label, the app does by sending a request to your server and reading the answer. That set of requests is the REST API, and you can use it too: from a script, a scheduled job, or another program, with no browser involved.

You do not need it to use Tesria. It is for the moment you think “I wish this happened by itself”. Some things people use it for:

• Publishing from another system. A build pipeline writes each release’s notes as a new page, so nobody has to copy them in.

• Reports. A script searches every morning for pages labeled needs-review and posts the list to your team’s chat.

• Tidying up in bulk. Adding a label to fifty pages is one short loop instead of fifty visits.

• Being told when something changes. A webhook has Tesria call your program the moment a page is published, updated or commented on.

A script signs in with an API token: a long secret, made on your profile, that lets it act as you. It sees exactly what you can see and can change only what you can change.

In this section