Brands

Brands are the foundation of content quality in Blogflair. Each brand represents one website/business context with its own settings, and those settings directly shape the quality, relevance, and consistency of generated topics and articles.

Why brand setup is important

A properly configured brand helps Blogflair:

• Generate content aligned with your actual site and audience
• Suggest more relevant internal links and topic angles
• Keep voice/tone consistent across articles
• Reduce manual rewrites and cleanup after generation
• Avoid low-context or generic output

In short: better brand setup = better drafts.

Required settings

Brand name

Use your real brand/business name.

• Appears throughout your content workflow
• Helps maintain consistent identity in generated drafts

Site URL

Your canonical website domain (for that brand).

• Anchors generation context to the right site
• Helps avoid cross-brand confusion if you manage multiple brands

Sitemap URL

The sitemap Blogflair uses to discover page URLs.

• Powers internal-link workflows
• Improves context for topic/article generation
• Keeps references grounded in real pages you own

Content settings

Language

Controls the language used in generated outputs.

Brand tone

Controls writing voice (e.g., professional, casual, technical).

Set this intentionally—tone has a large impact on draft quality and edit effort.

Article type

Defines output depth/length (e.g., Essential vs Complete).

• Essential: Faster, shorter drafts
• Complete: More depth and structure

Pick the default that matches your publishing style and team workflow.

Best practices

• Keep one brand per site/business context.
• Always use a valid, up-to-date sitemap.
• Revisit tone/article type after reviewing a few generated drafts.
• If quality drops, verify brand URL/sitemap and internal-link setup first.

Content API (per brand) for developers

The Content API is configured inside each brand and exposes that brand's published article content as a read-only endpoint.

Who can use it

• Starter and Pro plans can enable Content API.
• Free plan cannot enable Content API.
• Availability is checked by your current plan, and disabling the feature removes API access for that brand.

What it returns

The endpoint returns:

• Brand info (name, slug)
• That brand's generated articles (with content and metadata fields)
• Only article records that have generated content

Endpoint shape

Brand settings shows your exact endpoint URL. The route pattern is:

• /publisher/[username-or-userId]/[brandSlug]/articles

Example URL:

• https://blogflair.com/publisher/your-username/your-brand-slug/articles?apiKey=YOUR_CONTENT_API_KEY

Authentication options

You must provide the brand Content API key in one of these ways:

• Query parameter: ?apiKey=<key>
• Header: X-Content-API-Key: <key>
• Header: Authorization: Bearer <key>

If the key is missing or invalid, the request is rejected.

Sample requests

Using query parameter:

curl "https://blogflair.com/publisher/your-username/your-brand-slug/articles?apiKey=YOUR_CONTENT_API_KEY"

Using X-Content-API-Key header:

curl "https://blogflair.com/publisher/your-username/your-brand-slug/articles" \
  -H "X-Content-API-Key: YOUR_CONTENT_API_KEY"

Using Bearer token:

curl "https://blogflair.com/publisher/your-username/your-brand-slug/articles" \
  -H "Authorization: Bearer YOUR_CONTENT_API_KEY"

Key lifecycle and safety

• When you enable Content API, Blogflair creates a key for the brand (if missing).
• You can regenerate the key from the brand screen.
• The full key is shown once after generation/regeneration, then only masked.
• Keys are stored hashed server-side and validated on request.
• Treat keys like secrets and rotate them if exposed.

Practical usage tips

• Keep API enabled only for brands that need external consumption.
• Use key rotation during team/offboarding changes.
• If calls fail, verify plan eligibility, brand slug, and key source first.

Common setup issues

• Wrong site URL or outdated sitemap
• Missing sitemap entirely
• Tone too vague (causes inconsistent voice)
• Using one brand config for multiple different products/sites

Fixing these usually improves output immediately.