Modules

Modules

What the eight modules do, their endpoint counts, and where their API references start.

Blesyum is made of eight modules. Each is a separate service with its own endpoint family; identity, error and pagination contracts are shared.

ModuleBase pathWhat it does
Core/api/v1Account, workspace, team, billing, domains, branding, API keys, webhooks
CRM/api/crm/v1Contacts, conversations, live chat, help centre, campaigns
ERP/api/erp/v1Accounting, inventory, manufacturing, finance, e-documents
Commerce/api/shop/v1Products, orders, shipping, storefront, marketplaces
B2B/api/b2b/v1Dealer portal, wholesale orders, accounts, quotes
Call Center/api/callcenter/v1Calls, campaigns, IVR, recordings, CDR
Mail/api/mail/v1Mailboxes, domains, aliases, filters
Advisor/api/musavir/v1Taxpayers, filings, archive, accruals
Ads/api/ads/v1Campaigns, audiences, creatives, conversions

Public API or panel endpoint

Every module's endpoints fall into two groups, marked with a badge in the reference:

  • API key — endpoints designed for external automation, stable
  • Session — the panel's own endpoints; they work with your own account token

Today the module with a full public API is CRM (/api/crm/public/v1). Other modules' endpoints can be called with a panel session and are listed in the reference with their full records — but the public-API stability guarantee currently applies to CRM only.

We don't hide that distinction, because hiding it would mean letting you build a permanent integration on an endpoint that may change. If you need a public API for a specific module, tell us through support — real demand sets the order.

Module licence

To call a module's endpoints your workspace must be licensed for it. Without a licence the endpoint returns 403 with the module_not_licensed hint.

To see your licensed modules:

bash
curl "https://accounts.blesyum.com/api/v1/modules" \
  -H "Authorization: Bearer <session-token>"
Bu sayfa işine yaradı mı?