The marble work REST API lets you drive your organization from the outside: create clients, projects and tasks, build task chains made of AI and human steps, manage agents, skills and knowledge, and fetch results. Typical uses are custom scripts, automation platforms and external AI agents.

<aside> 🚀 The REST API and MCP server require the “Rocket” plan.

</aside>

<aside> 🤖

Working with an AI agent such as Claude Code, Cursor or another MCP client? Then the MCP server is the more convenient route: the same operations as ready-made tools, no HTTP code required. See the page marble work » MCP-Server 🇺🇸

</aside>

Base URL

All requests go to:

<https://api.marblework.app>

There are only two HTTP methods: GET (read) and POST (create). Requests and responses are JSON (Content-Type: application/json).

Tasks are started in the app. Through the API you create tasks including their step chain and read back status and results; a person triggers the actual run inside marble work. This keeps your team in control of when AI runs incur cost.

Quickstart

curl -s <https://api.marblework.app/clients> \
  -H "Authorization: Bearer mw_xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx"

Response:

{
  "data": [
    {
      "id": "0b6d…",
      "name": "Acme Inc",
      "slug": "acme-inc",
      "email": "[email protected]",
      "phone": null,
      "website": "<https://acme.com>",
      "contact_person": "Lisa Example",
      "created_at": "2026-08-01T09:12:00+00:00"
    }
  ]
}

Authentication

Creating an API key

API keys are created by an organization admin in the app under Settings → Organization → API access. When creating a key you pick its scopes (see below). The key is shown in plain text exactly once; after that it cannot be retrieved again. Store it safely, for example in a password manager or secret store.

A key always belongs to exactly one organization. Which organization a call affects is determined solely by the key; there is no organization parameter.