Household identity resolution and audience enrichment. Resolve any IP, MAID, or lat/long to a persistent household ID — then pull geo, segment visits, and CTV publisher exposure.
Base URL: https://api.quorum.live Auth: Authorization: Bearer <your-token> Health: GET https://api.quorum.live/health (no auth required)
Tokens are agency-scoped — all data returned is automatically filtered to your agency footprint. Tokens are stored as SHA-256 hashes server-side and cannot be retrieved after issuance.
| Method | Path | Description | Auth |
|---|---|---|---|
| GET | /health | Service + Snowflake status | — |
| POST | /v1/resolve | Resolve IP / MAID / lat-long → household ID + all MAIDs | Bearer |
| GET | /v1/household/{id}/geo | Census block, ZIP, DMA, state for a household | Bearer |
| GET | /v1/household/{id}/visits | Segment visits (fraud-filtered, enriched with 30-day visitor counts) | Bearer |
| GET | /v1/household/{id}/publishers | CTV/OTT publisher exposure by day | Bearer |
| GET | /v1/segments/catalog | Tracked locations with POI metadata for an advertiser | Bearer |
| GET | /v1/segments/{md5}/visits | Per-device visits for a specific segment (deduplicated) | Bearer |
| GET | /v1/segments/stats | 30-day rolling visitor counts per segment | Bearer |
Full interactive docs with try-it-live: https://api.quorum.live/docs
A persistent H3 resolution-12 cell ID (prefix 631xxx, NUMBER type). Multiple MAIDs and IPs map to a single household. This is the primary join key across all enrichment endpoints.
Mobile Advertising Identifier (UUID). Multiple MAIDs map to one household. The /resolve endpoint returns all MAIDs at a resolved household for cross-device matching.
Quorum's internal identifier for a tracked physical location (e.g. a specific restaurant). Use /v1/segments/catalog to enumerate all segments for your advertiser.
Your token is scoped to your agency ID. All queries are automatically filtered — you only see data from your agency's impressions and segments.
curl -X POST https://api.quorum.live/v1/resolve \
-H "Authorization: Bearer $TOKEN" \
-H "Content-Type: application/json" \
-d '{"input_type": "ipv4", "value": "72.14.192.1"}'
curl https://api.quorum.live/v1/household/631234567890/geo \ -H "Authorization: Bearer $TOKEN"
curl "https://api.quorum.live/v1/household/631234567890/visits?advertiser_id=1234" \ -H "Authorization: Bearer $TOKEN"
| Code | Meaning |
|---|---|
401 | Missing or invalid Bearer token |
404 | No household found for the given identifier |
422 | Invalid request body or query params (see detail field) |
429 | Rate limit exceeded |
500 | Internal error — contact api@quorum.live |
This API is in closed beta. Submit a request and you'll receive your token within one business day.
Request Access View Swagger UI