Zuuna REST API: build on your board
The open reference to the Zuuna REST API: zk_live_ tokens, eleven scopes, 3,000 requests per minute, endpoints and idempotency (readable without an account).
For developers
Read the API first, then decide
Whether a tool is any good shows in its interface, not on its pricing page. So the reference is open: tokens and scopes, the events Zuuna sends, and a CLI that works out which card a commit belongs to. No account, no form.
The reference
Webhooks: 22 events, delivered signed
Which events Zuuna sends, how to verify the signature (HMAC-SHA256 over the raw body), and what happens when a delivery fails.
CLI: link commits to cards without an OAuth app
One bash file, MIT-licensed on GitHub: a post-commit hook, releases from git tags, and the rule for when a card key means work and when it is only a reference.
A token, not a bot account
The usual tracker integration wants an OAuth app and a bot account with write access to your whole organisation (a lot of blast radius for the question of which card a commit belongs to). Zuuna issues a token with exactly the scopes you need, and you revoke it when you are done. What a token may do is in the scope table.
What is open here, and what is not
These pages cover the stable part: authentication, scopes, limits, the event catalogue and the signature scheme. The complete endpoint reference, with every field, lives in the app under Developers, because it changes with every release and a second hand-maintained copy would eventually be wrong. Incorrect API documentation is worse than none.
The whole thing, as a page
How a commit becomes a card movement (branch, pull request, release and deploy gate included) is written up once: kanban with git integration. The reference above is the tooling for it.
One commit, one card, nothing retyped.
Mint a token, install the CLI, commit. 14 days of full access, no card.