Brand Alignment: fact add
POST /v1/brands/:brand_id/alignment/facts
Access is limited to the brands permitted by your credential. Requires write:alignment. Workspace API keys and signed-in MCP sessions are supported.
Writes require an active workspace entitlement and an Idempotency-Key header. Support memberships cannot write. Fact slots and scanned-fact editing limits also apply.
Asky manages the monitoring questions. Responses include fact results and answer evidence without exposing generated question text.
Request body
Only the fields below are accepted. Brand and fact identifiers in the URL cannot be overridden in the body.
| Field | Required | Description |
|---|---|---|
text | Yes | The fact, one plain statement in the brand’s own words, up to 300 characters. |
category | Yes | The category it belongs to (the program endpoint lists them); a new name creates the category. |
subcategory | No | A subcategory inside the category, optional. |
countries | No | ISO country codes it is checked in. Default: the program’s current locations. |
language | No | ISO 639-1 code of the language the fact is asked in (en, de, nl, …). |
product_id | No | The product or service it is about (Brand Profile, Products & services); null or omitted for a brand-wide fact. |
Response
The standard API envelope places the program, overview, fact detail or write confirmation in data, with request metadata in meta.
Scan identifiers come from the program endpoint. Historical scans keep their original evidence. A setup edit applies to future scans.