Takeover API
The same engine as the site, over REST: fan overlap, where a fanbase is strongest, who to book in a city, brand matches, and full plans. Machine-readable description: /api/v1/openapi.json (OpenAPI 3.1).
Create a key in your workspace under Settings → API. It is shown once; Takeover keeps only a hash. Send it on every request:
curl -H "Authorization: Bearer tk_…" "https://<host>/api/v1/overlap?a=Phoebe%20Bridgers&b=PEN15"
- Enterprise: 60 requests a minute, 10,000 a month, 10 keys
{
"data": "…",
"evidence": {
"requests": [
"the Qloo requests behind the figures"
],
"method": "how each figure is computed"
},
"attribution": {
"source": "Qloo",
"text": "Taste data from Qloo",
"url": "https://www.qloo.com",
"note": "Scores and rankings are computed by Takeover from Qloo data."
},
"meta": {
"quota": {
"used": 12,
"limit": 500
}
}
}◆ Qloo signal Show the attribution (“Taste data from Qloo”, linked to https://www.qloo.com) wherever you display the data. Capacity, dates, prices and fees are never in the data: they are always to confirm.GET /api/v1/overlap
How strongly each fanbase's fans over-index on the other (Qloo affinity both ways), and the cities where both are strong.
a (required): First name: an artist, comedian, show, podcast, film or team.b (required): Second name.aId: Qloo entity id for a, from a previous choose answer.bId: Qloo entity id for b.Example: /api/v1/overlap?a=Phoebe%20Bridgers&b=PEN15GET /api/v1/fanbases/cities
Where a fanbase is strongest, market by market, from Qloo heatmaps scored by the engine.
q (required): The fanbase.entityId: Qloo entity id, from a previous choose answer.Example: /api/v1/fanbases/cities?q=John%20MulaneyGET /api/v1/venues
Who people in a city over-index on, by kind (music, comedy, podcast, brand): who to book there.
city (required): A city name, e.g. Austin or Manchester, UK.kinds: Comma-separated: music, comedy, podcast, brand. Default music,comedy.Example: /api/v1/venues?city=Austin&kinds=music,comedyGET /api/v1/brands/matches
Talent, shows and podcasts a brand's fans over-index on, scored by the engine, and the brand's strongest cities.
q (required): The brand.entityId: Qloo entity id, from a previous choose answer.Example: /api/v1/brands/matches?q=Liquid%20DeathPOST /api/v1/plans
Runs the Takeover agent for a fanbase in the background and saves the plan to your workspace. Answers 202 with a job id; poll GET /plans/{planId}.
query (required): The fanbase.entityId: Qloo entity id, to skip the name match.Example: /api/v1/plans {"query": "Phoebe Bridgers"}GET /api/v1/plans/{id}
The job's status (queued, running, failed) or, when done, the plan: partner, city, venue and sponsors with their scores, the brief and the outreach drafts.
id (required): The planId from POST /plans.Example: /api/v1/plans/3f1c…