Saku Developers

Quick start

1. Create a free Saku account, no credit card required.
2. Upgrade your workspace to Max from billing to enable API keys.
3. Create a scoped API key in Boards, Settings, API as a team administrator.
4. Read the OpenAPI description for endpoints, payloads, and permissions.
5. Make requests to https://saku.ie/api/v1 with the key in an Authorization header.

curl https://saku.ie/api/v1/boards \
  -H "Authorization: Bearer YOUR_SAKU_API_KEY"

Developer resources

• REST API guide, including authentication, examples, and rate limits.
• OpenAPI 3.1 specification and the API endpoint alias.
• Authentication reference and API catalog.
• Webhook guide for receiving Saku events.
• MCP server guide for AI clients.
• Hosted Streamable HTTP MCP endpoint: https://saku.ie/mcp, described by the MCP server card.
• Protected resource metadata listing every API key scope.
• Saku for AI assistants, a plain guide to what Claude, ChatGPT, or Cursor can do in your workspace.

Versioning and deprecation

The current REST API version is v1, served under /api/v1. We add endpoints and response fields within v1, so ignore fields you do not recognise. Breaking changes ship under a new path version, such as /api/v2.

Before we retire an endpoint, we will post a changelog note at least 90 days ahead, and responses from that endpoint will carry Deprecation and Sunset headers. The full policy is in the REST API guide.

Agents and sandboxing

Agents should begin with llms.txt and use the API only for a workspace that the user has explicitly authorised. Confirm before a mutation, keep API keys out of URLs and logs, and honour rate-limit headers. Use a separate Saku test workspace for integration development so test data never affects a production client workspace.

Need help?

See the Saku documentation or contact support with the endpoint, request ID where available, and a safe description of the issue. Do not include API keys or customer data in a support message.