eTermin
BUSINESS · CALENDAR
Appointments, calendars, services and free slots on their own booking page.
Connecting eTermin in practice
eTermin signs every request instead of sending a bearer token: three headers — `publickey`, `salt` and `signature` — where the signature is a base64-encoded SHA256 of a freshly generated random salt keyed with your secret. A generic HTTP connector that only knows how to attach a static credential cannot call it at all, and API access starts on the Pro plan.
Scopes that draw scrutiny
publickey / secret key pair (eTermin’s own terms)There is no scope mechanism. The public key identifies the booking account and the secret key signs the request, and together they reach appointments, calendars, services and free slots.
Worth knowing
- A fresh salt per request means requests cannot be replayed — and also that a naive retry layer which re-sends a captured request body will be rejected rather than duplicated.
- The resource list lives on SwaggerHub rather than on etermin.net, so the endpoint reference and the authentication description are on different sites.
- API access is a plan feature ("Offene Schnittstellen (API)") from Pro upward, so the same integration is simply unavailable to an account on the tier below.
- The documentation is German-first, and the base URL is the booking host itself (https://www.etermin.net/api/{resource}) rather than a dedicated API domain.
Checked against eTermin API (2026-09-29), eTermin plans and features (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put eTermin behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.