Other ways in

The API is not the only way to reach Polder from outside. These all use it, or sit next to it.

The backlog command line#

A Go client (backlog, in the cli/ folder of the repository) that speaks nothing but the API described here. It is the quickest way to try an endpoint without writing curl, and a good model of a well-behaved client: scoped tokens, an explicit workspace, and PATCH requests that send only what changed.

Raycast#

An extension in raycast/ covers issues, projects, cycles, saved views, the knowledge base and the inbox. Several endpoints exist because it needed them: ?q= on issues, /members, /inbox, /saved-views/{view}/issues, /favorites.

Webhooks#

Backlog calls you when something happens (issue created, status changed, comment posted), signed so you can verify the sender. Administrators set them up under Settings → Webhooks; events, payloads and signature verification are on the Webhooks page.

The MCP server, for AI clients#

One connection covers Backlog, Docs and Chat: https://mcp.polder.work/mcp. The client signs in with OAuth, you pick the workspace and the scopes, and it acts as you. Many API actions exist as MCP tools too (polder_create_issue, polder_list_issues, polder_send_message), and the pages in this documentation name them where they match. The one difference to know: no tool sends a mailing. Sending is the REST API's notify:send scope, so a person decides.

claude mcp add --transport http polder https://mcp.polder.work/mcp

Set-up for other clients is under Settings → Connected apps in Backlog, which shows the right address with a copy button.