Conceptual Guide
Understand the trust boundaries first.
This section contains no code. It explains the data flow between Frigolive, your backend service, and your white-label interface — along with service identity, tenant isolation, error behaviour, and production responsibilities.
The integration in short
Client credentials carry only the selected accounts and explicitly granted scopes; the client secret is shown exactly once.
The long-lived client secret is exchanged for a short-lived access token and is never sent to a browser or mobile app.
Every request is re-checked against the token scope, the credential account allow-list, and the real tenant ownership of the resource.
You own your users and your screens; Frigolive provides only the narrow, versioned data contract.
Documentation vs. API reference
This section describes decisions and behaviour. You will not find request code, JSON bodies, or copy-paste samples here. Exact URLs, parameters, five backend languages, the live try-it panel, and detailed response contracts live in the API Reference.
The API reference lists every contracted customer endpoint. Access does not depend on visibility — it depends on a short-lived access token, its scopes, the account allow-list, and tenant isolation.
Suggested reading order
Start with the Integration Journey, then read Service Identity & Tokens and Scopes & Isolation. If you are building an interface, continue with Web, Mobile & BFF; if you are planning an event-driven backend, read Events & Webhooks. Before going live, read Errors & Resilience.