Your brand
Everything your customers see says your name. Set it once in the console, or programmatically — onboarding customers by API and then being told to upload a logo by hand would defeat the point.
What it covers
| Field | Where it shows up |
|---|---|
display_name | Anywhere a name is rendered on your behalf. |
logo_url | Onboarding screens and emails. https only. |
primary_color, accent_color | The two colours those surfaces are built from. Hex. |
email_from_name | The sender name on emails sent to your customers. |
support_email | Where your customers reply. Their questions reach you, not us. |
domain | The domain your customers know you at. |
Setting it
curl -X PATCH https://api.kleos.click/v1/brand \
-H "Authorization: Bearer kls_live_..." \
-H "Content-Type: application/json" \
-d '{
"display_name": "Acme Dialer",
"logo_url": "https://cdn.acme.example/logo.svg",
"primary_color": "#0B1F3A",
"accent_color": "#C8A24A",
"support_email": "help@acme.example"
}'Send only what you want to change. Send null to clear a field. Colours must be hex and URLs must be https — an http logo would downgrade every page it appears on, including your customers' onboarding.
What stays ours
Kleos never appears in your API responses, your customers' emails, or the screens they use. What we do not do is pretend the underlying platform is yours in a legal sense: your reseller agreement covers what you may claim, and compliance disclosures required by law on a call are the law's wording, not a branding surface.