July 2026

July brought one thing, and it is a foundation rather than a feature. Uku’s public API is now a full read-write interface to nearly all of the product. Everything built on Uku from the outside runs on it: reporting tools, syncs, automations, and the AI assistant that followed in September.

API v3 is out, and it is not a version bump. The old v1.0 was a read-oriented window onto part of Uku. Version 3 is a full read-write interface to nearly all of it. Projects, budgets, notes, attachments, flextime and delegations had no v1.0 endpoint at all.

Why? Anything your firm wants Uku to do that Uku does not do yet, you can now build or buy. Connect a reporting tool, sync a warehouse, drive Uku from Zapier or Make, or let your own AI tooling work through it.

What is new:

• Signing in is two headers, X-Uku-Company and X-API-Key, with no token to refresh. The old v1.0 exchanged a key and secret for a JWT that expired in 10 minutes.
• Keys can be narrower than you. Scope a key Read, Edit or All. Give it an expiry date, or lock it to your own servers with an IP allowlist.
• Financial data is a separate tick, not a scope. A read-only key can see money, and a read-write key need not.
• Personal keys act as one member. Every request is limited to what that person sees in Uku, while an integration key behaves the same whoever triggers it.
• Errors carry stable codes your integration can branch on, instead of a sentence to match on.
• Interactive documentation at app.getuku.com/api/v3/docs, with a machine-readable OpenAPI spec.
• Webhooks fire on writes made through API v3.

Worth knowing: v1.0 is frozen rather than switched off, so your existing integrations keep working. Keys are not interchangeable, so a v1.0 key will not authenticate against v3.

Getting started: an Elite feature. Company Owners and Company Admins generate keys under Settings & Apps → Public API. Public API v3