API
Ortszeit has a REST API. It was built for the mobile apps — the offline queue, the photo uploads, the quota state they show before you hit a limit — and it is reachable today.
It is not a stable public API yet. Endpoints and payloads change with the apps, without a deprecation period, because the only clients are shipped by us. Build against it if you like, but pin nothing to it that you would be upset to see break. The interface that is a contract is the portable format — that one has a version field and a documented deprecation path, and it is deliberately where the promises are.
Schema
The OpenAPI schema is generated from the code and served at:
https://accounts.ortszeit.app/api/schema/That document is the reference. Anything written on this page that disagrees with it is out of date.
Authentication
Two ways in:
-
A user API key, sent as a header:
Authorization: Api-Key <your-key> -
A session cookie, which is what the web editor itself uses.
Everything is scoped to the signed-in user’s single blog. There is no
cross-account access, and there is no public read API for other people’s blogs
— published blogs are already public HTML, with RSS at /feed/ and JSON Feed
at /feed.json, which is the right interface for reading someone’s writing.
Roughly what is there
Trips, posts, media upload, place lookup and confirmation, the end-of-trip
prompt, quota state, and the export and
import jobs. Quota rejections come back as 403 with a
human-readable message naming the limit that was hit, so a client can show it
without inventing its own wording.
Consult the schema for the actual paths, parameters and shapes.
No posting API in the other direction
Ortszeit does not post to Instagram, TikTok, YouTube or Google Maps on your behalf, and it is not going to. Sharing goes through your phone’s own share sheet: it costs one extra tap, works with everything installed on the device, and does not break when a platform changes its rules.