API overview and authentication
You do not need the API to use Leadovaro: the dashboard covers setup and day-to-day operation. Reach for the API when you want to script configuration, pull data into your own systems, or build on top of what Leadovaro knows. The same capabilities are exposed to AI clients through the MCP server.
Base URLs
- REST API:
/_sites/product.leadovaro.com/api - MCP endpoint:
/_sites/product.leadovaro.com/mcp(see the MCP server page; members of several workspaces can pin one with?tenant=<tenantId>)
Authentication
The API is authenticated with Leadovaro Auth bearer tokens
(Authorization: Bearer <jwt>).
The JWT identifies the caller, not the tenant. Leadovaro resolves the active tenant from the caller's memberships on every request:
- One membership: that tenant is selected implicitly; no header needed.
- More than one: send
X-Leadovaro-Tenant: <tenantId>naming one of your tenants. - Multi-membership with the header missing:
403 ambiguous_tenant. - A tenant you don't belong to:
403 tenant_forbidden.
note
The X-Leadovaro-Tenant header is a selector, not the source of truth: the
tenant bound at the data layer is always taken from the matched
membership.