---
title: "Get AI-referral session timeseries"
method: GET
path: "/api/mcp/projects/{projectId}/traffic/referrals"
tags: ["Traffic"]
---

# Get AI-referral session timeseries

`GET /api/mcp/projects/{projectId}/traffic/referrals`

First-party AI-referral session timeseries (from the Searchable tracker) — one point per day with a per-platform session breakdown, plus window totals. Returns 409 traffic_not_connected if no source is connected. `days` defaults to 30, max 365.

## Path parameters

- `projectId` string, uuid, required

## Query parameters

- `days` integer
- `platform` string

## Response `200`

AI-referral session timeseries.

- TrafficReferralsResponse
  - `points` object[], required
    - `date` string
    - `byPlatform` object[]
      - `platform` string
      - `sessions` integer
      - `newVisitors` integer
  - `totals` object, required
    - `sessions` integer
    - `newVisitors` integer
    - `byPlatform` object[]
      - `platform` string
      - `sessions` integer
      - `newVisitors` integer
  - `dateRange` DateRange, required — The resolved lookback window for this response.
    - `from` string, date-time, required
    - `to` string, date-time, required

## Other responses

- `400` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `401` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `403` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `404` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `409` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.
- `429` — Rate limited. Usually the per-API-key REST limit (600 requests/minute); on Google-backed endpoints it can also relay an upstream Google rate limit. `Retry-After` (seconds) is present when the limit was applied by Searchable's own rate limiter; it may be absent when an upstream provider rate-limits.
- `504` — Error response. `code` is the machine-readable reason — see the [error reference](/api/errors) for the full catalog and remediation per code.

---

[API](https://skmtc.net/searchable/apis/searchable-rest-api.md) · [All operations](https://skmtc.net/searchable/apis/searchable-rest-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/searchable/searchable-rest-api/revisions/301b04e800ed/schema)