Event management API and MCP: read your events in code, or run them from your AI assistant.
WebMobi has two doors for software. The REST API reads one of your events — its sessions, speakers, sponsors and ticket types — with an API key. The MCP server lets Claude or another MCP client create, edit and publish events and their programmes from chat, and every change it makes is recorded in the event’s History.
REST: read an event with one call · MCP: events, sessions, speakers, sponsors, exhibitors · changes recorded
What it is
If you want your own website, a data pipeline or a script to read what is in a WebMobi event, use the REST API: one authenticated call returns the event and its programme as JSON. If you want to build and change events by talking to an AI assistant, connect it to WebMobi’s MCP server: it can list your events, create drafts, add sessions and speakers, import a spreadsheet and publish — acting as you, on events you manage.
This page is for the developer or operations lead deciding what can be automated: the exact endpoint and fields, how keys and connections work, the full list of assistant tools, the controls on every change, and what neither door does.
WebMobi Event App Builder · Build and launch your event app yourself.
WebMobi Event App Builder is a self-service event app builder that helps conference organizers, associations, agencies and event teams create and launch branded event apps — with registration, check-in (including offline check-in and walk-ins), session attendance, agenda, speakers and exhibitors in one platform.
The REST API: reading an event
Send a GET request with your key in the Authorization header. The call reads one event by its id and returns it with everything on its programme.
GET https://events.webmobi.com/api/v1/events/{event-id}
Authorization: Bearer wm_live_…| In the response | What it holds |
|---|---|
| id, slug, title, description | The event’s identity, its web address and its text. |
| status, event_mode, status_label | Whether it is a draft or published, Test or Live, and the label shown for it. |
| start_at, end_at, timezone | When it runs, and the time zone it runs in. |
| format, is_free, location_city, location_country | In person or virtual, free or not, and where. |
| published_at, created_at, updated_at | When it was published, created and last changed. |
| sessions | Every session, each with the speakers linked to it, their role and their order. |
| speakers | Every speaker on those sessions, once each. |
| sponsors and tickets | The event’s sponsors and its ticket types. |
Keys
- In the dashboard on events.webmobi.com, open Settings → API keys and choose Create new key.
- Give the key a name you will recognise, such as “Website build”.
- Copy the key — it starts wm_live_ and is shown once. WebMobi stores only a hash of it.
- The list shows each key’s name, prefix, scopes, when it was last used and when it was created; Revoke stops a key immediately.
Answers you should handle
- 401 — no key, or a key WebMobi does not recognise. The message says to send
Authorization: Bearer wm_live_…. - 404 — the event does not exist, or it was not created by the account the key belongs to. The two are deliberately indistinguishable.
- 429 — more than 60 requests in a minute from this key. Wait for the Retry-After seconds.
Errors come back as { "success": false, "error": { "code", "message" } }, and every response carries the X-RateLimit headers.
MCP: running your event from an AI assistant
MCP (Model Context Protocol) is how AI assistants such as Claude use outside tools. WebMobi’s MCP server is at https://events.webmobi.com/api/mcp. There are two ways to connect:
- One click, with OAuth. In Claude, add a custom connector with just that address. You sign in to WebMobi and approve one consent screen; there is no key to copy.
- With an API key. Any MCP client can send the same
Authorization: Bearer wm_live_…header the REST API uses. The connect page has the configuration for remote clients and for Claude Desktop.
Ask the assistant to call webmobi_whoami first: it confirms the connection and shows your plan and limits. Then ask in plain words — “give me a template for my sessions and speakers”, “here is my agenda, import it”, “publish the event as a test”. Worked conversations are in the MCP guide and the connect your AI guide.
The tools the assistant gets
| Group | Tools |
|---|---|
| Look things up (read only) | webmobi_whoami, webmobi_list_my_events, webmobi_get_event, webmobi_search_events, webmobi_get_demo_event, webmobi_list_event_registrations, webmobi_list_sessions, webmobi_list_speakers, webmobi_list_sponsors, webmobi_list_exhibitors, webmobi_list_tickets, webmobi_get_import_templates |
| Events | webmobi_create_event (a draft), webmobi_update_event, webmobi_publish_event (Test or Live — you must choose), webmobi_clone_event, webmobi_archive_event (reversible) |
| Programme | Create, update and delete sessions, sponsors and exhibitors; create and update speakers, and remove a speaker from an event |
| Bulk and images | webmobi_bulk_import, webmobi_bulk_import_from_url (up to 500 rows per import), webmobi_upload_image |
| Drafting with WebMobi’s AI | webmobi_ai_generate_event and webmobi_ai_create_event draft an event from a description using WebMobi’s own AI, so they depend on your plan |
The controls on every change
Letting software change a live event is only safe if the limits are clear. These are the ones WebMobi enforces on every MCP call:
| Control | What it means |
|---|---|
| It acts as you | Every action runs as the account that owns the key or approved the connection. |
| Only events you manage | Content changes reach events you could edit in the dashboard: ones you created, your organization’s events if you are an owner or admin, and events where you are a teammate with Edit event. Publishing, archiving and cloning are limited to events you created; cloning also works on WebMobi’s demo event. |
| A write needs write access | A connection that only has read access is refused when it tries to change anything. |
| Publishing asks Test or Live | There is no default. A test event shows a TEST EVENT banner and its registrations do not count; going live with test registrations asks whether to keep or delete them. |
| Archive, never hard delete | An event can be archived, which is reversible. Deleting an event is not available over MCP. |
| One audited write path | Every content change goes through the same server function as the dashboard’s AI editing, which applies the change and its audit record together — a change whose record cannot be saved is not saved. |
Your team’s access shapes what an assistant can reach, because it acts as the person who connected it. See team permissions.
What neither door does
- Neither the REST API nor MCP adds, edits or removes registrations, checks anyone in, changes ticket types or handles payments.
- The REST API reads one event at a time; it has no call that lists your events and no endpoints for sessions, speakers, registrations or check-ins on their own.
- WebMobi does not send webhooks to your systems when something changes.
- Attendee lists and attendance reports are CSV exports in the dashboard, not API responses.
For those, the dashboard is the place: registration on event registration, and the attendance exports on session check-in.
What it does not do
Written down here so you find out now, not on event day.
The REST API does not edit your programme or your attendees
It has no endpoints for sessions, speakers, sponsors, exhibitors, tickets, registrations or check-ins. Use MCP or the dashboard to make changes.
The REST API reads only events your account created
An event you manage as an organization admin or a teammate, but did not create, answers 404 to your key.
Exhibitors, registrations and check-ins are not in the REST response
The response carries the event, its sessions with speakers, its sponsors and its ticket types.
No webhooks
There is nothing to subscribe to. Poll the API, or export from the dashboard.
60 requests a minute per key
Over the limit you get a 429 with Retry-After.
No published API reference yet
This page and the connect guides are the documentation today.
Deletes over MCP are real
Deleting a session, sponsor or exhibitor removes it; History keeps the removed record so you can see what was lost, but it cannot restore it.
The two AI drafting tools depend on your plan
They use WebMobi’s own AI. Every other tool works with your assistant’s own model.
Read the step-by-step guides
The screens, labels and checks for each step are in the product guide on events.webmobi.com.
Build the program
Sessions, speakers and sponsors — by hand or by spreadsheet, and what an import never does.
Bulk import sessions, speakers, sponsors, exhibitors and attendees
An import adds and updates but never deletes; matching, file limits, column mapping, the Event Info sheet.
Event History and check-in audit trail
Who changed the event and who checked in whom — staff member, device, offline or not, repeat scans.
What each plan includes is on the pricing page.
FAQ
Does WebMobi have an API?
Yes. A REST API reads one of your events with its sessions, speakers, sponsors and ticket types, authenticated with an API key you create in the dashboard. Changes are made through the MCP server or the dashboard.
Can I connect Claude to WebMobi?
Yes. WebMobi runs an MCP server at https://events.webmobi.com/api/mcp. In Claude, add a custom connector with that address and approve WebMobi’s consent screen, or connect any MCP client with an API key.
What can an AI assistant change through MCP?
Events (create, update, publish as Test or Live, clone, archive), and their sessions, speakers, sponsors and exhibitors — one at a time or in bulk from a spreadsheet. It can read registrations and ticket types but not change them.
Can an assistant change registrations, check-ins or payments?
No. There are no MCP tools that add, edit or remove registrations, check people in, change ticket types or touch payments. Those stay in the dashboard.
Are changes made by an AI assistant recorded?
Yes. Every change goes through the same audited write path as the dashboard’s own AI editing and is recorded in the event’s History with what it was before and after. Changes made through AI name the person the assistant acted for.
Can the REST API list all my events or return registrations?
No. The REST API reads one event at a time by its id and returns its programme and ticket types, not its registrations or check-ins. An assistant connected over MCP can list your events and an event’s registrations.
Does WebMobi send webhooks when someone registers?
No. WebMobi does not offer webhooks you can subscribe to today. Read the event through the API, or export attendee lists from the dashboard.
Is there a rate limit?
Yes. Each API key may make 60 requests a minute. Every response carries X-RateLimit-Limit, X-RateLimit-Remaining and X-RateLimit-Reset headers, and a request over the limit gets a 429 with a Retry-After header.
Connect your assistant to a real event.
Create an event, connect Claude with one consent screen, and ask it to show you the demo event and import your agenda.