Eventee
BUSINESS · CALENDAR
One event’s agenda, speakers, partners, and attendee check-ins in that account.
Connect Eventee with Fabriq Developer
Your user pastes their Eventee credential on a page Agentic Fabriq hosts, so it never reaches your backend and never becomes one shared key across all of your users. Same call as OAuth, one more argument.
Provider names are surfaces, not vendors, and the authoritative list is the capabilities endpoint rather than any page including this one — an unknown name returns 400 with the valid list. Fabriq Developer is free to start and needs no provider paperwork. Start free or read the quickstart.
Connecting Eventee in practice
API access is included on every Eventee plan, but the plan caps attendees per event — 200 on Essential, 500 on Signature, 1,000 on Professional — so an agent syncing check-ins is working inside a licence counter rather than an open dataset, and a bulk import fails on that counter rather than on a validation error. Everything is scoped to a single event, so a multi-event account is several disjoint datasets.
Rate limits
- No request-rate figure is published. The documented ceilings are attendee counts per event: 200, 500 and 1,000 on the single-event plans, and 500, 1,000 and 3,000 per event on the annual Team, Business and Enterprise plans.
Worth knowing
- The Apiary-hosted reference returns nothing but its title to a fetcher, so parameters have to be read in a browser and cannot be looked up at run time.
- Everything is scoped to one event, so a multi-event account is several disjoint datasets rather than one, and an agent has to be told which event it is working in.
- Attendee headroom is bought in blocks of 100 as a per-event add-on, which means a bulk import can fail on a licence limit rather than on a validation error.
Checked against Eventee pricing (2026-09-29), Eventee (2026-09-29), Public Eventee API (Apiary) (2026-09-29)
What an agent can do
Each action is granted on its own. An agent allowed to read is not thereby allowed to write, and the scope beside each row is what the acting user must have connected for it to run at all.
Often connected alongside
Put Eventee behind one governed endpoint.
Same permissions, same audit trail, whatever else you connect next.