Saku Developers

Connect an integration or AI agent to Saku's REST API and MCP tools. Use a scoped API key, start with the OpenAPI description, and request only the permissions needed for the task.

Quick start

Create a free Saku account, no credit card required.
Upgrade your workspace to Max from billing to enable API keys.
Create a scoped API key in Boards, Settings, API as a team administrator.
Read the OpenAPI description for endpoints, payloads, and permissions.
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://mcp.saku.ie/mcp.

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.