White-label reports use a versioned branding object instead of reading live app styles or raw profile settings directly. The export renderer receives aDocumentation Index
Fetch the complete documentation index at: https://docs.neariq.io/llms.txt
Use this file to discover all available pages before exploring further.
PdfBrandTokens snapshot, renders from that snapshot, and stores the same snapshot with the export record.
This keeps exported reports reproducible after an agency changes its logo, colors, contact details, or after the NearIQ app design changes.
Token shape
Source settings
The branding settings saved from the app are normalized before they can be used by report exports.| Key | Type | Notes |
|---|---|---|
company_name | string | Max 80 characters |
tagline | string | Max 120 characters |
logo | string | HTTPS URL or image data URL, max 200 KB encoded |
primary_color | hex color | Optional; falls back to accent |
accent_color | hex color | Optional; falls back to NearIQ blue |
font_family | enum | Inter, DM Sans, Arial, Helvetica, Georgia |
heading_font_family | enum | Same enum |
website | HTTPS URL | Optional |
email | Optional | |
phone | string | Max 30 characters |
address | string | Max 200 characters |
footer_text | string | Max 160 characters |
legal_text | string | Max 240 characters |
chart_palette | hex color array | 3 to 8 colors |
Export rules
- Build branding tokens before rendering.
- Enable white-label branding only after server-side plan and permission checks pass.
- Store the exact token object used for each export so the file can be reproduced later.
- Do not render directly from raw settings.
- Do not render directly from app CSS variables.
- If validation fails, use NearIQ’s default branding tokens.