Backlog is automatable through its API

Backlog is automatable today through Nulab's v2 API. Calls go to /api/v2/ on a space host such as example.backlog.com or example.backlogtool.com. An API key can be sent as the apiKey query parameter or the Backlog-API-Key header. OAuth 2.0 uses the authorization-code grant and then an Authorization Bearer access token that expires in 3600 seconds. The overview says the API can get or update issues, wiki pages, and files, and can manage projects and users. Each method is still limited by the caller's space or project role and by restrictions such as view-only. Webhooks POST when an issue, comment, wiki page, file, or Git or Subversion change is added or updated. Nulab documents an official Java library, Backlog4j. Nulab also publishes backlog-mcp-server, which runs over stdio or streamable HTTP and calls the API with BACKLOG_DOMAIN and BACKLOG_API_KEY. Its tools cover projects, issues, comments, milestones, wiki pages, Git repositories, pull requests, and notifications. Zapier, Make, Power Automate, and n8n were not opened. No Backlog CLI was established. Computer-use viability is unassessed. The API scores 8 and the MCP server scores 7. The API is the best path because any HTTPS client can call it, including with OAuth, without running the MCP process.

Best path today: api · Overall automatability: 8/10