Quorum Data API

Store-visit measurement and location data for agencies and their advertisers. Send us your advertisers and store lists, track each store's status, pull visit records, and read the numbers on your published Quorum reports.

v2.1.0
API version
28-day
Default attribution window
k≥3
Report privacy floor

Base URL & Auth

Base URL:  https://api.quorum.live
Auth:      Authorization: Bearer <your-token>
Health:    GET https://api.quorum.live/v1/health  (no auth required; /health also works)

Tokens are bound to one agency and can only read that agency's advertisers. A token may have an expiry date (an expired token gets 401) and may be read-only (POST /v1/intake/* then returns 403). Tokens are stored as SHA-256 hashes and cannot be shown again after issue. Device- and household-level routes are not available to partner tokens; use the Quorum MCP (https://mcp.quorum.live/mcp) for those questions. Details: Access and scope.

Main endpoints

MethodPathDescriptionAuth
GET/v1/healthService status (alias: /health)—
GET/v1/advertisersYour agency's advertisers, with Quorum advertiser idsBearer
POST/v1/intake/advertisersSend your advertisersBearer
POST/v1/intake/locationsSend your stores (add-only)Bearer
GET/v1/intake/locationsEach store's status: submitted, pending or activeBearer
GET/v1/advertisers/{advertiser_id}/locationsTracked locations for your advertiserBearer
GET/v1/advertisers/{advertiser_id}/locations/{segment_md5}/visitsVisit records for one locationBearer
GET/v1/advertisers/{advertiser_id}/reportThe numbers on your published reportBearer
GET/v1/partner-feed/dailyDaily exposure and visit counts, JSON or CSVBearer

Every route, with fields and examples: https://api.quorum.live/documentation · try it live: https://api.quorum.live/docs

Key Concepts

Your advertiser id vs. Quorum's

Intake takes your own DSP advertiser id. /locations, /visits and /report take it too, or a Quorum id your agency owns. The analytic roll-ups, performance tables and partner feed take the Quorum advertiser id listed by GET /v1/advertisers.

Segment MD5

Quorum's id for a tracked location. GET /v1/intake/locations lists the segment_md5s for each of your active stores, and /locations lists every location tracked for the advertiser.

Agency scope

Your token sees only your agency's advertisers. Another agency's advertiser is refused (403) or not found (404), never served.

Quick Start

1. Check the service

curl https://api.quorum.live/v1/health

2. List your advertisers

curl https://api.quorum.live/v1/advertisers \
  -H "Authorization: Bearer $TOKEN"

3. List the tracked locations for one of your advertisers

curl "https://api.quorum.live/v1/advertisers/12345/locations" \
  -H "Authorization: Bearer $TOKEN"

Status Codes

CodeMeaning
202Advertiser recognised but not mapped yet; retry later
401Missing, invalid or expired token
403Not allowed for this token: route not open to partners, advertiser outside your agency, or read-only token on a write
404Not found for your agency
410Advertiser disconnected by your agency; reconnect to restore
422Invalid request, or advertiser permanently not reportable (see detail)
503Temporarily unable to verify the request; retry

Get Access

This API is in closed beta. Submit a request and you'll receive your token within one business day.

Request Access View Swagger UI