Bot Access Incidents

GET /api/v1/bot-access-incidents returns the incidents Bot Access Monitoring has opened: one row per bot and monitored page that lost access, with the cause and its lifecycle. Incidents open when a check stops passing and resolve automatically when access recovers. The underlying checks are in bot access results.

Filters

Incidents are current-state data rather than a dated history export, so since / until are not supported on this resource. Standard parameters (limit, offset, format=csv) work as described in Pagination, filtering, and errors.

Key fields

• incident_id: stable identifier for the incident
• target_id: the monitored page that lost access
• crawler_id: the affected bot
• classification: the cause. robots_block means robots.txt disallows the bot; infra_block means the request was rejected before the page answered, typically a firewall or CDN bot rule; timeout and error cover unreachable pages
• block_vendor: for infra_block, the detected blocking layer when identifiable (for example cloudflare)
• status: open while the block persists, resolved once access recovers, muted when the workspace has silenced it
• first_seen / last_seen: when the block was first and most recently confirmed
• resolved_at: when access recovered, for resolved incidents

Rows are ordered by last_seen descending, so offset pagination is stable.

Example

curl -H "Authorization: Bearer $AEO_API_KEY" \
  "https://app.citlyze.com/api/v1/bot-access-incidents?status=open"

Use this resource to feed your own alerting or dashboards with the AI bots currently blocked from your pages, and to review how quickly past blocks were resolved.