Blesyum Developer

One platform, one API language, eight modules.

From a contact to an invoice, from a call to a campaign — you can read, write and subscribe to every record Blesyum produces. 8,814 endpoints, one identity model, one error contract.

Endpoints
8,814
Modules
11
Guides
18
First request
curl https://acme.crm.blesyum.app/api/crm/public/v1/contacts \
  -H "Authorization: Bearer blsk_..." \
  -H "Accept: application/json"
Response
{
  "data": "…",
  "trace_id": "01JC…"
}

Your first request takes two minutes

Create an API key in the panel and call your own workspace's address. The key's scopes decide which endpoints it opens — the scopes you pick when creating it appear here verbatim.

  1. 01Create a key in Panel → Developer → API Keys
  2. 02The address is your own workspace's module address
  3. 03Responses always come in a {data, trace_id} envelope

Modules

Every module has its own endpoint family; the identity, error and pagination contracts are shared.

Model Context Protocol

Let your AI read this documentation for you

An assistant connected to the Blesyum MCP server searches the guides, reads the endpoint catalogue and pulls scope and event lists — so the integration code it writes is grounded in real endpoints rather than invented ones.

Claude Code
claude mcp add --transport http blesyum https://apidocs.blesyum.com/mcp

Guides