Technical Enrichment

Triggers a technical audit of the brand's site, or accepts an already-run audit as JSON. Populates brand.technical_context (health score, pages crawled, issues by severity, crawl date), plus creates technical_issue insights and evidence that feed the leverage scoring multiplier for the technical_gap category (1.30x).

Duration: 5-20 minutes for a triggered audit, seconds for an upload.

Path parameters

Request body

You must provide one of the two modes below. Posting with no body, or with both fields omitted, accepts the request and returns 202 — but the background run will fail almost immediately because there is nothing to process. Always include either trigger: true or audit_data.

Response (202 Accepted)

{
  "run_id": "run-uuid",
  "status": "queued"
}

Poll GET /brands/{brand_id}/runs/{run_id} until status is done. On success, the run's meta contains:

{
  "insights_count": 47,
  "evidence_count": 47,
  "health_score": 87
}

And GET /brands/{brand_id} will now include a populated technical_context field.

Example — trigger a fresh audit

curl -X POST \
  -H "X-API-Key: $BM_API_KEY" \
  -H "Content-Type: application/json" \
  https://api.boringmarketing.com/brands/$BRAND_ID/enrich/technical \
  -d '{"trigger": true}'

Example — upload pre-collected audit

curl -X POST \
  -H "X-API-Key: $BM_API_KEY" \
  -H "Content-Type: application/json" \
  https://api.boringmarketing.com/brands/$BRAND_ID/enrich/technical \
  -d @audit.json

Errors