Guides
White Label & Branding
Customise the Total Access platform with your own branding and domain.
White Label & Branding
The White Label module allows clients to customise the Total Access platform with their own branding, custom domain, and CORS origins.
Resolve branding for a domain
Check the branding configuration for a given domain:
curl -X GET "https://developer.totalaccess.co.za/api/v1/whitelabel?domain=acme.example.com" \
-H "Content-Type: application/json"Response:
{
"success": true,
"data": {
"client_id": 42,
"brand_name": "Acme Field Services",
"logo_url": "https://cdn.totalaccess.co.za/logos/acme.png",
"primary_color": "#1a56db",
"custom_domain": "acme.example.com",
"is_whitelabel": true
}
}This endpoint is public (no authentication required) so that the frontend can resolve branding before login.
Manage branding settings
Get current branding:
curl -X GET https://developer.totalaccess.co.za/api/v1/whitelabel/branding \
-H "Authorization: Bearer YOUR_JWT_TOKEN"Update branding:
curl -X PATCH https://developer.totalaccess.co.za/api/v1/whitelabel/branding \
-H "Authorization: Bearer YOUR_JWT_TOKEN" \
-H "Content-Type: application/json" \
-d '{
"brand_name": "Acme Field Services",
"logo_url": "https://cdn.totalaccess.co.za/logos/acme-new.png",
"primary_color": "#e11d48",
"custom_css": ".header { font-weight: 700; }"
}'CORS origins
White label clients can configure additional CORS origins for their custom integrations:
List allowed origins:
curl -X GET https://developer.totalaccess.co.za/api/v1/whitelabel/cors-origins \
-H "Authorization: Bearer YOUR_JWT_TOKEN"Add a new origin:
curl -X POST https://developer.totalaccess.co.za/api/v1/whitelabel/cors-origins \
-H "Authorization: Bearer YOUR_JWT_TOKEN" \
-H "Content-Type: application/json" \
-d '{ "origin": "https://portal.acme.example.com" }'CORS origin changes may take up to 5 minutes to propagate due to caching.