Platform
Agency
Run many client sites from one account, and let clients see their own data without seeing yours.
What it adds
- Clients — group websites under a client, so billing and reporting follow the relationship rather than the site list.
- Client users — give a client a login that sees only their own sites.
- White label — your name and colours on the dashboard the client logs into.
- Agency API keys — provision the above from your own systems instead of the dashboard.
Two ways to work
Everything is available in the dashboard under Agency, with no code. If you onboard clients from your own admin or a signup flow, the same operations are on the API — one request per client instead of a form.
Endpoints
Relative to /api/v1, authenticated with an X-API-Key header like the rest of the API.
/api/v1/user/agency/clients/api/v1/user/agency/client-users/api/v1/user/agency/white-label/api/v1/user/agency/api-keysNot a Bearer token, and no snt_age_ prefix
Authorization: Bearer snt_age_.... The server accepts X-API-Key, and keys are snt_ plus a site slice — there has never been an snt_age_ form. Creating and reading keys is covered in API keys.The write operations for each of these are in the catalogue described on the REST API page, generated from the router so it cannot describe a route that no longer exists.
Client portals
A client portal is a link that shows one client their own dashboard without an account. Useful for a monthly report you do not want to export by hand. Portal links are unguessable and are excluded from search engines.
Getting access
Agency features are part of the Agency plan — see the pricing page, or get in touch if you are moving a portfolio across.