Tenant Info
| Method | Path | Summary |
|---|---|---|
| GET | /__tenant-info | So the login page can brand itself for whichever tenant vanity domain it's being loaded on — {name, slug, domain}, or {tenant:null} on sso.brambleit.cloud / … |
#So the login page can brand itself for whichever tenant vanity domain it's being loaded on — {name, slug, domain}, or {tenant:null} on sso.brambleit.cloud / …
GET
/__tenant-infoSo the login page can brand itself for whichever tenant vanity domain it's being loaded on — {name, slug, domain}, or {tenant:null} on sso.brambleit.cloud / the bare apex, where there's deliberately no tenant to brand for. Safe to expose pre-auth: none of this (name, colors, wording, logo) is sensitive — it's the same stuff visible in the hostname/rendered page itself. branding is null when the tenant hasn't customized anything (server-provided defaults kick in client-side).
- Address
https://<your-org>.brambleit.cloud/__tenant-info- Requires
- None: public, or protected by a token in the address or body.
Response 200
| Field | Type | Description |
|---|---|---|
tenant | any | |
branding | any |
Example response
JSON
{
"tenant": null,
"branding": null
}Example request
JavaScript
// From a page served by Bramble (uses the signed-in session)
const res = await fetch('/__tenant-info', {
method: 'GET',
credentials: 'include',
});
const data = await res.json();Was this page helpful?
Thanks for your feedback.