API Responses

You should be receiving 200s from our log endpoints. If not, here’s what the other statuses mean.

Scenario	Status returned
Missing or invalid API key	401
API key inactive, or org-level instead of project-level	403
Malformed auth header (bad Bearer token / invalid JWT)	401
Missing or malformed request body	400
Unexpected internal error	500
Valid request, but all events filtered out (not AI crawler traffic)	200 (by design)
Valid request, events accepted and queued	200

Event outcome details

A 200 response means your request was accepted and every accepted event was queued for processing. It does not mean the events are already visible in your dashboard — persistence happens asynchronously and typically completes within seconds. Every successful response includes a details object that tells you exactly what happened to each event you sent:

{
  "success": true,
  "details": {
    "outcome": { "received": 4, "accepted": 2, "dropped": 2 },
    "results": [
      { "index": 0, "status": "accepted" },
      { "index": 1, "status": "dropped", "reason": "INVALID_TIMESTAMP" },
      { "index": 2, "status": "accepted" },
      { "index": 3, "status": "dropped", "reason": "NON_AI_USER_AGENT" }
    ]
  }
}

outcome — aggregate counts: received (events in your request), accepted (queued for processing), and dropped (filtered or rejected). received always equals accepted + dropped.
results — one entry per event, in the same order as your request body. index is the zero-based position of the event in the array you sent. If you send a single event object instead of an array, you get one result with index: 0.
status — accepted (queued) or dropped (not stored).
reason — a stable machine-readable code explaining why an event was dropped. Present only on dropped results.

If your dashboard stays empty while you receive 200 responses, check details.outcome.accepted — if it is 0, the reason codes tell you why each event was filtered.

Drop reason codes

Reason	Meaning
`NON_AI_USER_AGENT`	The user agent doesn’t match a known AI crawler or search engine bot. This is the most common reason — regular browser traffic is filtered by design.
`DISALLOWED_PATH`	The request path or content type isn’t consumable content (e.g. static assets like CSS, JS, images).
`INVALID_TIMESTAMP`	The `timestamp` value isn’t a parseable date.
`INVALID_HOSTNAME`	The `hostname` is missing, an IP address, or otherwise invalid.
`INVALID_EVENT_SCHEMA`	The event failed validation against the crawler log schema (e.g. missing required fields, invalid status code).
`INVALID_PROVIDER_SCHEMA`	The record failed validation against the CDN provider’s log format.
`MISSING_USER_AGENT`	The record has no user agent, so it can’t be classified.
`MISSING_CLIENT_IP`	The record has no client IP (e.g. PII exclusion is enabled in your log drain).
`MISSING_CONTENT_TYPE`	No content type was provided and none could be inferred from the path.
`INVALID_URL`	The record’s request URL couldn’t be parsed.
`HOSTNAME_MISMATCH`	The event hostname doesn’t match the project’s configured website.
`WORKER_SUBREQUEST`	Cloudflare Worker subrequest — a duplicate of the main Logpush event.
`NON_TRAFFIC_LOG`	Netlify log record that isn’t a traffic log (e.g. function or deploy logs).
`NON_PROXY_LOG`	Vercel log record without proxy data (e.g. build or runtime logs).

Notes

The details key is also used on 400 error responses, where it contains validation issues for the malformed request instead of the outcome object.
The AWS CloudFront (Firehose) endpoint uses the response format required by Amazon Data Firehose and does not include outcome details.
Validation/handshake requests sent by CDN providers when connecting a log drain return details with zero counts and an empty results array.

Overview

CDN Providers

Platform

Reference

Event outcome details

Drop reason codes

Notes

​Event outcome details

​Drop reason codes

​Notes

Event outcome details

Drop reason codes

Notes