canonical: https://jentic.com/apis/eventmobi.com/eventmobi

# EventMobi API

The EventMobi API provides programmatic read access to events, attendees, and sessions on the EventMobi event mobile app platform. Three operations cover listing events, retrieving attendees per event, and listing sessions per event, which is enough surface for syncing event programmes and attendee rosters into other systems. Authentication is via API key, and the API is best suited to feeding mobile event app data into reporting tools, AI assistants, and partner integrations.

## For AI agents

Read EventMobi events, list attendees per event, and list sessions per event for reporting and downstream sync.

## Scope

Does not handle registration creation, push notifications, or in-app content authoring - use for reading EventMobi events, attendees, and session schedules only.

## Capabilities

- Retrieve a list of EventMobi events for an organisation
- List attendees for a specific event by event ID
- List sessions and their schedules for a specific event
- Pipe attendee rosters into post-event marketing or analytics tools
- Surface session schedule data in agent-facing assistants and dashboards

## Use cases

### Mobile App Programme Sync

Mirror the EventMobi event programme into an internal portal or analytics warehouse so non-mobile users can browse the agenda and so reporting can join attendance to other data. The events and sessions endpoints give the canonical schedule, and the attendees endpoint provides the roster. Initial integration takes a few hours.

Example prompt: Pull all sessions for event 'evt_123' from EventMobi and write them to the internal agenda page database with start time, end time, and title

### Post-Event Attendee Reporting

Feed the EventMobi attendee roster into a BI tool to report on registration mix, opt-in rates, and follow-up engagement. The `/events/{eventId}/attendees` endpoint returns the structured roster so analytics teams can produce sponsor reports without manually exporting CSVs from the event app. Reports are typically ready within a day of the event closing.

Example prompt: Pull the attendee list for event 'evt_123' from EventMobi and produce a CSV grouped by registration type for the sponsor report

### AI Agent Integration via Jentic

An AI conference assistant can answer attendee questions like 'when is the AI track keynote?' by calling the EventMobi sessions endpoint through Jentic. Jentic search resolves the natural-language intent to the right operation, and the vault holds the API key. The assistant is wired up in well under an hour.

Example prompt: Search Jentic for 'list eventmobi sessions', load the operation, and answer 'what time is the AI track keynote at event evt_123?'

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/events` | List events for the account |
| GET | `/events/{eventId}/attendees` | List attendees for an event |
| GET | `/events/{eventId}/sessions` | List sessions for an event |

## Key resources

- **Events** — List events for an organisation
- **Attendees** — List attendees for a specific event
- **Sessions** — List the session schedule for a specific event

## Why Jentic

- **Setup:** Wiring EventMobi by hand means learning its API key in the Authorization header, tracking the api.eventmobi.com/v4 base path, and coding the event, attendee, and session reads yourself. Through Jentic you install once, import the EventMobi API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** EventMobi puts the event id in the URL path (`/events/{eventId}/attendees`), so a rule can pin your agent to one event: it can read that event's attendees and sessions and nothing else. Every operation is read-only here, and the agent only gets the ones you place in the allowed set.
- **Credential handling:** Your EventMobi API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list eventmobi sessions' or 'read event attendees', and Jentic returns the matching EventMobi operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Cvent API** — Enterprise event platform with mobile app, registration, and venue sourcing
- **Swoogo API** — Event registration and microsite platform for marketers
- **Eventleaf API** — Add registration, contact lists, and session attendance alongside an EventMobi mobile app
- **Slack API** — Push EventMobi schedule and attendee updates into Slack channels

## FAQ

### What authentication does the EventMobi API use?

The EventMobi API uses an API key (ApiKeyAuth scheme). When invoked through Jentic, the key sits in the encrypted vault and is injected at execution time, so it never enters the agent's prompt or logs.

### Can I list sessions per event with the EventMobi API?

Yes. GET `/events/{eventId}/sessions` returns the session list for an event, including start and end times. This is the right endpoint for building agenda views or syncing the schedule into another system.

### What are the rate limits for the EventMobi API?

The OpenAPI spec does not declare explicit rate limits. Treat the API as standard for event SaaS and back off on HTTP 429; consult the EventMobi developer docs for the latest published limits before bulk syncs.

### How do I pull attendee rosters through Jentic?

Search Jentic for 'eventmobi attendees', load the GET `/events/{eventId}/attendees` operation, and execute it with the event ID. Install with pip install jentic and use the async search, load, execute flow.

### Does the EventMobi API expose registration creation?

The current spec exposes read access to events, attendees, and sessions only. Registration creation, push notifications, and app content authoring are managed in the EventMobi platform rather than this API surface.

### Can I limit what my agent is allowed to do with the EventMobi API?

Yes. Because you run Jentic One yourself, your own rules decide which EventMobi operations and credentials the agent may use, so you place only the operations you want into its allowed set. Every operation here is read-only (list events, list attendees for an event, and list sessions for an event), and since the event ID sits in the URL path such as GET `/events/{eventId}/attendees`, a rule can pin the agent to a single event so it reads that event's attendees and sessions and nothing else. The stored API key is injected at execution time and never enters the agent's prompt or logs.