WHR
Request API access
API & MCP · BUILT FOR AGENTS

The event participation index.

Ask any company where it will be. Ask any event who will be there.

Request API accessRead the docs
GET /v1/company/{domain}/events?upcoming=true

{
  "company": "acme-robotics.com",
  "events": [
    {
      "event": "AUTOMATICA",
      "role": "exhibiting",
      "dates": "2027-06-22 / 06-25",
      "city": "Munich"
    },
    {
      "event": "iREX",
      "role": "speaking",
      "dates": "2027-12-02 / 12-05",
      "city": "Tokyo"
    },
    {
      "event": "SPS",
      "role": "sponsoring",
      "dates": "2027-11-10 / 11-12",
      "city": "Nuremberg"
    }
  ]
}
LIVE ENDPOINT · INDICATIVE FIELDSMCP ENDPOINT AVAILABLE
QUERIED IN PRODUCTION BY
InformaAmadeusFornovaGuidebookAzavistaEventifyLuxembourgNubreed
→ COMPANY TO EVENTS

Where will this company be?

Full participation footprint — exhibiting, speaking, sponsoring, hosting. History and confirmed upcoming.

→ EVENT TO COMPANIES

Who will be at this event?

Every mapped participant, by role, per edition.

// EVERYTHING ELSE IS A FILTER ON THESE TWO

1M+
BUSINESS EVENTS
2.5M+
BUSINESS EVENT EDITIONS
100M+
COMPANIES & INFLUENCERS
100+
COUNTRIES
12
YEARS OF EVENT HISTORY

Participant-level records run three years deep and grow daily. We'd rather tell you that than have you find out.

You could build this. Here's what it costs.

Event participation isn't published by companies — it's published by events. To answer "where will these 500 accounts be," you have to index the events first, extract every exhibitor list, resolve name variants to entities, and track editions as they change.

That cost is the same whether you're tracking 500 companies or 50,000. It's the index, not your slice of it.

We maintain it once, for everyone.

THE INDEX · WHAT "INCLUDED" MEANS
event indexevery event, every edition, tracked as they changeCONTINUOUS
exhibitor extractionevery list, per site, as formats shiftONGOING
entity resolutionname variants → one company, one eventTHE HARD PART
edition trackingthe layer that breaks quietly when self-builtMONITORED
GET /v1one API on top of all of itYOU ARE HERE
BUILD IT
WHR API
Initial index
3–6 months engineering
Day one
Exhibitor extraction
Per-site, ongoing
Included
Entity resolution
The hard part
Included
Edition tracking
Breaks quietly
Included
Coverage
Whatever you built
Global

// It's not that you can't. It's that it degrades silently, and you won't know.

"CES," "Consumer Electronics Show" and "CES Las Vegas" are one event with 58 editions.

Siemens AG, Siemens Energy and Siemens Healthineers are three different participants.

Getting that wrong is the difference between a list and an index.

"CES""Consumer Electronics Show""CES Las Vegas"↓ RESOLVEDevent_id: ces · 58 EDITIONS
Which events will our customers’ accounts attend?
GTM & ENRICHMENT
Is this supplier commercially active, and where?
AI AGENTS
Which shows are worth the budget?
EVENT & FIELD MARKETING
What’s driving occupancy in this city that week?
TRAVEL & HOSPITALITY
FREE
100 companies or events / mo
Request access
GROWTH
from $100 / month
Volume tiers, all fields
Start
PLATFORM
Embed for your users
Volume rates, MCP endpoint
Talk to us

// PRICED PER ENTITY, NOT PER CALL · SEARCH AND RESOLUTION ARE UNMETERED

Request access. Query 100 companies free.

Start·MCP ENDPOINT AVAILABLE·Docs