https://<festival>.fesutibaru.com/api/v1. The examples use demo.
1. Sign in
The full API is used signed in as a person, with OAuth. An agent that supports it finds the sign-in on its own: a request without a sign-in is answered401 with a WWW-Authenticate header pointing at /.well-known/oauth-protected-resource, which names the sign-in server and the two permissions:
The person signs in to Planner and agrees. From then on the agent sends
Authorization: Bearer <token>.
2. Read
?edition=2026 for another.
3. Propose a change
201 with the proposal’s id. The person now sees it in their inbox, with the field’s value now and what you proposed, and accepts or rejects it. Check what happened with GET /api/v1/proposals/<id>.