Skip to main content

White-Label

White-label mode lets you present Influgen under your own brand. It is intended for agencies, managed service operators, and enterprise deployments that need a client-facing surface.

Plan requirement​

White-label configuration currently requires the Agency plan.

Config fields​

White-label config supports:

  • logo_url
  • favicon_url
  • brand_name
  • primary_color
  • secondary_color
  • accent_color
  • custom_domain
  • custom_css
  • footer_text
  • support_email

Domain management endpoints​

  • GET /api/v1/white-label/config
  • PUT /api/v1/white-label/config
  • POST /api/v1/white-label/domains
  • GET /api/v1/white-label/domains
  • POST /api/v1/white-label/domains/{id}/verify
  • DELETE /api/v1/white-label/domains/{id}

Domain verification flow​

When you add a custom domain, Influgen creates a TXT verification record. The record moves through states such as:

  • pending_dns
  • pending_certificate

The high-level process is:

  1. Add the custom domain.
  2. Create the required TXT record in DNS.
  3. Verify the domain from Influgen.
  4. Wait for certificate issuance.
  5. Route traffic to the verified hostname.

[screenshot: White-label settings screen with brand colors, logo uploader, domain table, and DNS verification instructions]

Best practices​

  • use stable hosted assets for logo and favicon
  • keep custom CSS minimal unless you have a strong QA loop
  • verify DNS before client launch dates
  • make support email and footer text explicit so end users know who owns the experience