Pragence

Branding and Custom Domains

The API includes organization branding controls for company name, logos, colors, font family, theme, custom CSS, and custom-domain configuration. These endpoints require an authenticated organization administrator for changes. The repository does not define the plan matrix, add-on prices, or guarantee that a particular branded experience is included in your agreement.

Configure branding

Use the branding endpoints for your organization:

  • GET and PUT /api/v1/branding/organizations/{org_id}/branding to read or update branding fields.
  • GET /api/v1/branding/themes to list the available theme presets.
  • POST /api/v1/branding/organizations/{org_id}/logo to upload a logo, and DELETE on that path to remove it.
  • GET /api/v1/branding/organizations/{org_id}/css-variables to retrieve the generated CSS variables.

The upload route accepts an image file subject to the limits in the running API schema. Do not assume a dashboard menu or particular file-size limit unless it is present in your deployed console and /openapi.json.

Configure a custom domain

The branding API provides endpoints to add, inspect, verify, and remove an organization custom domain:

  • POST /api/v1/branding/organizations/{org_id}/domain
  • GET /api/v1/branding/organizations/{org_id}/domain
  • POST /api/v1/branding/organizations/{org_id}/domain/verify
  • DELETE /api/v1/branding/organizations/{org_id}/domain

The domain status response includes the CNAME target and any SSL status or validation records available in that deployment. Configure DNS and certificate handling according to the returned instructions and your hosting provider. Successful DNS verification alone does not guarantee that TLS termination or all application routes have been configured for the domain.

Commercial access and deployment support for branding and custom domains must be confirmed with your administrator. See the live API reference for the request schemas.

On this page