Skip to main content
GET
Get human traffic from AI assistants

Authorizations

Authorization
string
header
required

A Searchable API key, created under Settings → Workspace → Integrations. Send as Authorization: Bearer sea_xxxxx. Every key carries one or more scopes (read, write, admin) and may optionally be bound to a single project — see Getting started.

Path Parameters

projectId
string<uuid>
required

The project id.

Query Parameters

days
integer

Lookback window in days. Default and maximum vary by endpoint — see the operation description.

Required range: x >= 1
from
string

Start of an absolute window (inclusive, UTC). Accepts YYYY-MM-DD or a full ISO timestamp. Requires to, and is mutually exclusive with days — sending both returns 400 invalid_argument. A range longer than the endpoint's maximum is rejected rather than clamped.

Example:

"2026-03-01"

to
string

End of an absolute window (inclusive, UTC). Accepts YYYY-MM-DD or a full ISO timestamp. Requires from.

Example:

"2026-03-31"

host
string

Comma-separated hostnames to narrow the report to. Useful on multi-domain projects; omit for every host in the project.

Example:

"blog.acme.com"

Response

Human traffic summary with the AI-referred breakdown.

Human sessions arriving from AI assistants. The summary and aiReferral halves can come from different sources — check summarySource.

summarySource
enum<string>
required

unavailable means no first-party beacon is installed: every summary field is null and the AI figures came from GA4, which shares no denominator with it.

Available options:
beacon,
unavailable
summary
object
required
aiReferral
object
required
dateRange
object
required