API

Cobblr has a REST API under /api/v1. Everything the web app does goes through it, so anything you can do in the UI you can do from a script or another service.

Shape

• JSON in and out, over /api/v1/....
• Bearer token auth. A session token for the browser, or a long-lived API token for scripts and integrations.
• Workspace-scoped. Most routes hang off a workspace and a module, like /api/v1/orgs/<workspace>/modules/<module>/..., so a token acts as its owner, in the workspaces its owner belongs to (scopes narrow what it may do, not where).
• OpenAPI. The API describes itself with an OpenAPI spec, so you can generate a client or browse the endpoints rather than guessing.

Tokens

Create an API token from the app and store it somewhere safe (it's shown once). By default a token acts as the person who created it. You can also mint it with scopes, which restrict it to a specific set of routes and nothing else, so a token for one job can only do that job.

Claude and MCP

For working on a workspace conversationally, Cobblr also ships an MCP server that wraps this API for your own Claude. See Connecting Claude.

There's deliberately no hand-written endpoint list here: the OpenAPI spec is the reference, and because it's generated from the running instance, it can't drift from reality.