canonical: https://jentic.com/apis/eventee.com/eventee # Eventee Public API The Eventee Public API builds and maintains a conference agenda and its attendees on the Eventee event platform. Your agent creates halls, lectures, and breaks to lay out the schedule, adds and updates speakers and partners, and manages tracks that group sessions. It also handles the audience side, inviting registrations and attendees, checking attendees in, and reading back participants, content, and reviews for the event. ## For AI agents Build a conference agenda on Eventee: create halls, lectures, and breaks, manage speakers, tracks, and partners, and invite, check in, and read back attendees. ## Scope Does not sell tickets, process payments, or stream sessions. Use for managing conference agenda, speakers, and attendees only. ## Capabilities - Create halls, lectures, and breaks to lay out the event schedule - Add and update speakers for the event - Invite registrations and attendees and check attendees in - Manage tracks and labels that group sessions - Add and update event partners - Read back event content, participants, and reviews ## Use cases ### Agent-Driven Agenda Building An AI agent connected through Jentic assembles a conference agenda by creating halls, adding lectures to them, and inserting breaks between sessions. Because Eventee models each schedule element as its own operation, the agent lays out a full day of programming and attaches speakers to the sessions it created. Example prompt: Create a hall, add two lectures to it, and attach a speaker to each lecture ### Attendee Onboarding An events team onboards attendees by inviting registrations, inviting attendees, and checking them in on arrival. The Eventee API exposes invite and check-in operations and reads back participants, so an agent drives registration through to door check-in and reconciles who actually attended. Example prompt: Invite a batch of attendees, then mark one as checked in and confirm it in the participants list ### Speaker and Partner Management A conference organiser keeps speakers, tracks, and partners current as the programme changes. The API creates and updates speakers, tracks, and partners, letting an agent add a late-addition speaker, slot their talk into a track, and register a new sponsor as a partner. Example prompt: Add a new speaker, assign their session to a track, and register a new partner for the event ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/content` | Get all event content | | POST | `/hall` | Create a new hall | | POST | `/lecture` | Create a new lecture or workshop | | POST | `/speaker` | Create a new speaker | | PUT | `/attendee/invite` | Invite attendees | | GET | `/registrations` | Get all registrations | | GET | `/participants` | Get all participants | | GET | `/partners` | Get all partners | ## Key resources - **Halls and lectures** — Create halls, lectures, workshops, and breaks on the schedule - **Speakers** — Create and update event speakers - **Attendees** — Invite registrations and attendees and check attendees in - **Tracks and labels** — Create and update tracks that group sessions - **Partners** — Create, update, and list event partners - **Content and reviews** — Read event content, participants, and reviews ## AI readiness This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use. - **Score:** 52 / 100 - **Maturity:** Foundational - **Dimensions:** - Foundational Compliance: 99 / 100 - Developer Experience & Jentic Compatibility: 79 / 100 - AI-Readiness & Agent Experience: 26 / 100 - Agent Usability: 94 / 100 - Security: 50 / 100 - AI Discoverability: 64 / 100 - **View full report:** https://jentic.com/apis/eventee.com/eventee/scorecard - **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/ - **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview ### Score it yourself Every API in the directory is allowlisted, so you can re-score it with no key required. - **Score your own API:** https://jentic.com/scorecard.md - **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md ```sh npx @jentic/api-scorecard-cli score ``` ## Why Jentic - **Setup:** Wiring the Eventee Public API by hand means generating a token in the admin console and formatting the Authorization header as a bearer value on every call. Through Jentic you install once, import the API from the API Directory, store the token once, and your agent calls the agenda and attendee operations. - **Permission scoping:** Eventee carries the hall, lecture, and speaker ids in the URL path, so a rule can scope your agent to operations on specific sessions. You choose the operations it may call, so destructive ones like deleting a lecture or speaker are not included unless you add them. - **Credential handling:** Your Eventee token is held by your own Jentic One instance, encrypted, and injected into the Authorization header at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'create a lecture' or 'invite attendees', and Jentic returns the matching Eventee operation with its input schema so the agent builds the agenda or manages attendees correctly. ## Related APIs - **4.events API** — Another event management platform API, an alternative for running agendas and attendees. - **aEvent API** — An event and webinar automation platform, an alternative when sessions are primarily virtual. - **AddEvent API** — Calendar and add-to-calendar links that complement Eventee by pushing sessions into attendees' calendars. ## FAQ ### What authentication does the Eventee Public API use? The Eventee Public API authenticates with an API token sent in the Authorization header in the form `Bearer YOUR_API_KEY`, per its OpenAPI spec, and you generate the token in the Eventee admin settings. Through Jentic the token is held by your own Jentic One instance and attached at execution time, so it never appears in your agent's prompt or logs. ### Can I build a conference agenda with the Eventee Public API? Yes. The API creates halls, lectures, workshops, and breaks, adds speakers, and manages tracks that group sessions. Your agent can lay out a schedule and attach speakers to the sessions it created, then adjust the programme as it changes. ### What are the rate limits for the Eventee Public API? The OpenAPI spec does not specify rate limits. Check the Eventee documentation at https://eventee.com for the current limits before running bulk agenda or attendee operations. ### Is there an Eventee MCP server? You do not need an MCP server to give your agent the Eventee Public API. Jentic connects it directly from the API Directory: import it, store your token once, and your agent discovers the agenda and attendee operations it needs on demand without loading an extra server's tool definitions into its context. ### Can I limit what my agent is allowed to do with the Eventee Public API? Yes. Eventee carries the hall, lecture, and speaker ids in the URL path, so a rule can scope your agent to operations on specific sessions. You choose the operations it may call, so destructive ones like deleting a lecture or speaker stay out unless you add them, and every call it makes is logged. ### How do I build an Eventee agenda through Jentic? Install the Jentic One command line with `curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh`, then add the Eventee Public API from the Jentic directory and search by intent such as 'create a lecture in a hall'. Jentic returns the matching operation with its input schema so your agent builds a valid request. To run it on your own infrastructure, install Jentic One from its GitHub repo.