Docs
The Acta HTTP API
Anything that can send an HTTP request can use Acta: scripts, forms, CI jobs, Zapier or n8n. The API serves the MCP server's tools as plain JSON at https://acta.aaenz.no/api/v1/<tool>, with the same keys and the same checks. A key can do exactly as much as it can over MCP.
What a key can do
curl https://acta.aaenz.no/api/v1 -H "Authorization: Bearer <key>"
The answer lists every tool the key may use, with its arguments as JSON Schema and whether it takes GET or POST.
Reading
Tools that only read take GET, with their arguments in the query string. Lists repeat or use commas:
curl "https://acta.aaenz.no/api/v1/list_tasks?board=aaen-studios/acta&status=todo,review" \ -H "Authorization: Bearer <key>"
Writing
Tools that change things take POST, with their arguments as a JSON body:
curl https://acta.aaenz.no/api/v1/create_tasks \
-H "Authorization: Bearer <key>" -H "Content-Type: application/json" \
-d '{"board": "aaen-studios/acta", "tasks": [{"title": "Add CSV export", "labels": ["Feature"]}]}'
Answers and errors
- 200: the tool's result as JSON.
- 400: a mistake the caller can fix, with an
errorsaying what to change. - 401: the key is missing or was revoked.
- 403: the key's access doesn't cover the tool.
- 404: there's no tool by that name.
- 405: a tool that changes things was called with GET.
CORS is open, since every call needs a key.
Public roadmaps
To build a public roadmap into your own site, with its votes and ideas, use the roadmap API. Its keys reach only what the public page shows, so they can sit in a web page's code. The keys here act as you and can change anything you can, so keep them on a server.