Menu

Getting started

Create an API key, make your first request and write to the CRM in five minutes.

The MB Suite API is REST over HTTPS, with JSON in snake_case. Every request acts as a person of your organization —the one the API key represents or the one who authorized the app—, with their permissions and never more.

1. Create an API key

An owner or admin of the workspace turns on the API and the MCP in Settings → API & MCP → Turn on API & MCP. They are available on active paid subscriptions (not on the free trial) and apply to every Account of the workspace.
  1. 1Sign in to MB Suite as an owner or admin of the organization and open Settings → API & MCP → API keys.
  2. 2Choose Create API key: a name, who it represents (you, by default), the permissions per module (Read or Read and write) and, only if the integration deletes, Allow deletions.
  3. 3Copy the API key: it is shown only once (mbs_live_ and 46 characters). Store it as a secret, never in a web page's code or in a repository.

2. Your first request: who am I?

GET /v1/me returns the credential's living card: the person, the role, the organization, the scopes, the plan's limits, a short list of the Accounts it can reach (child_orgs_total says how many there are; GET /v1/orgs lists them) and, for each module it can use, how many operations and groups it has. The operations come from GET /v1/catalog: with module, that module's operations with their full descriptions (a large module, like crm, comes by groups: ask for one with group), and with ids_only=true, just the ids of all of them.

curl https://api.mb-suite.com/v1/me \
  -H "Authorization: Bearer $MB_API_KEY"

Keep the API key in an environment variable (MB_API_KEY). The base of every request is https://api.mb-suite.com/v1; the same API also answers at https://mb-suite.com/api/platform/v1.

3. Write to the CRM

Creating a deal needs the pipeline and the stage: look them up with GET /v1/crm/pipelines. Without owner_id, the deal belongs to the API key's person.

curl -X POST https://api.mb-suite.com/v1/crm/deals \
  -H "Authorization: Bearer $MB_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: 2f1c9a1e-7a52-4c8b-9d0e-acme-annual" \
  -d '{
    "title": "Plan anual — Acme",
    "value": 4800,
    "currency": "USD",
    "pipeline_id": "PIPELINE_ID",
    "stage_id": "STAGE_ID"
  }'

The response carries deal_id. The Idempotency-Key makes retrying the same request safe: it does not create two deals for 24 hours.

4. Get changes without polling

To know when a lead comes in or a deal changes stage, create a webhook in Settings → API & MCP → Webhooks: MB Suite sends a signed POST to your server. See Webhooks.

5. Connect an AI agent

Claude, ChatGPT, Cursor, VS Code, Claude Code and any MCP-compatible app connect to the MCP server (https://mcp.mb-suite.com) and work with the same operations and the same permissions. See MCP.

What's next