Authorization: Bearer <token>. There are two ways to obtain a token. Server integrations use client credentials. People using the Leadinfo MCP sign in with their Leadinfo account through OAuth; the MCP client takes care of that flow and the resulting token acts for the person who signed in.
Client credentials
1
Request a token
Call The response carries the token, its lifetime in seconds and the scopes granted to your client:Use
POST /v1/auth/token with your credentials in the request headers.expires_in from the response rather than a fixed number; lifetimes differ per client.3
Renew before expiry
Request a new token shortly before
expires_in seconds have passed. An expired or unknown token gets 401 Unauthorized.Scopes
Scopes are granted to your client by Leadinfo and appear in thescope field of the token response and of GET /v1/auth/me.
Identified visitors and Leadbot conversations are visible to anyone with
tracker:read, the same as in the Portal. A request that needs a scope the token lacks gets 403 Forbidden with the missing scope in the message.
Who a token acts for
GET /v1/auth/me tells you.
A client-credentials token acts for the company that owns the client. A token obtained by a person acts for that person’s company. Partner accounts see their own trackers and those of the companies they manage.
