Scheduling & Booking · Integration
AddEvent
Add AddEvent to your product for your customers, and give your AI agents governed access to it.
AddEvent's Calendar and Events API v2 is at api.addevent.com/calevent/v2 and takes the account API token as a bearer token, found in the account settings. The model is calendars containing events, plus calendar subscribers, who are people subscribed to a calendar feed rather than attendees of a single event, with RSVP data held separately against events. Because a subscription calendar is delivered as a feed, an event change reaches subscribers on their own client's refresh schedule, so an update is not instant even though the API call succeeded. Searches return paged result objects with a page_size, and events are queried rather than listed wholesale. On the category: events and bookings map well, but AddEvent has no availability concept, since it publishes and distributes events rather than finding free slots. fastn holds each customer's token, keeps calendar and event ids mapped and handles upkeep.
In your product
Embedded for your customers. Per-tenant auth, no per-customer code, maintained by fastn.
Let a customer connect their own AddEvent account so events created in your product appear on their published calendar
Publish a subscription calendar for a customer's audience and keep it updated as your own schedule changes
Read RSVP responses back into your product so organisers see attendance without checking two systems
Track calendar subscriber counts per calendar so marketing teams can see which feeds people actually follow
For your AI agents
Governed, audited access for the agents you build, through the MCP server.
Ask an agent to create an event on a named calendar and report back the add to calendar link
Have an agent update an event's time and note that subscribers will see it on their next feed refresh, with the change audited per tenant
Let an agent summarise RSVP responses for an upcoming event and flag low turnout
Example prompt
How many people have RSVPed to next Thursday's webinar, and how many subscribe to that calendar?
Set up AddEvent in 4 steps
- 01Enable the AddEvent connector from your fastn dashboard.
- 02Have each customer authorise their own AddEvent account, so calls run under their credentials rather than a shared key.
- 03Decide which bookings, events and availability your product needs, map those fields, then enable the actions and triggers you want.
- 04Call it from your product and expose it to your agents through the same governed connection.
Why teams use the AddEvent integration
What you get by embedding it with fastn instead of building it yourself.
- Ship an AddEvent integration without building it. Your customers connect their own AddEvent account inside your product and work their bookings, events and availability there, with no per-customer code on your side.
- Handle the part that actually costs time: availability is only true at the moment you read it, so a stale free/busy picture becomes a double booking somebody has to apologise for. fastn owns the auth, token refresh, rate limits, pagination and breaking-change fixes, so an AddEvent update is not your on-call problem.
- One integration serves your product and your agents. The same governed AddEvent connection powers in-product features and gives AI agents scoped, audited access, so you let people book and reschedule without leaving your product without wiring it twice.
Used by these teams
Compare with
Calendly
Google Calendar
AppointletOften used alongside
Tools the same teams tend to run next to AddEvent, across other categories.
Slack
Microsoft Teams
Twilio
AircallAddEvent integration FAQ
How do I add an AddEvent integration to my product?
Enable the AddEvent connector in your fastn dashboard, then let each customer authenticate their own AddEvent account. fastn handles the OAuth flow, token storage and refresh per tenant, so there is no AddEvent client code in your app and no per-customer branch in your codebase. Setup is 4 steps.
Do my customers each connect their own AddEvent account?
Yes. Every connection is scoped to the individual customer, so each authorises their own AddEvent account and only ever sees their own bookings, events and availability. That per-tenant isolation is the point of an embedded integration: you support the long tail of customer setups without maintaining an integration per customer.
Can AI agents use this AddEvent integration?
Yes. The same connection is exposed to your agents through the fastn MCP gateway, with permissions scoped per tenant and every call audited. Ask an agent to create an event on a named calendar and report back the add to calendar link
Who maintains the AddEvent integration?
fastn does. When AddEvent changes an endpoint, deprecates a field or alters its auth, the fix lands in the connector rather than in your backlog, and your customers' connections keep working.
Can my product create, reschedule or cancel bookings in AddEvent automatically?
Yes, in each customer's own account. Your product reads live availability, places a booking, moves it or cancels it, and reacts when someone books or cancels on the other side.
Does it respect each team's own availability rules in AddEvent?
Yes. Working hours, buffers, lead times, resource capacity and routing rules are configured per customer and mapped rather than hard-coded, so an unusual setup works without code from you.
What can I build with the AddEvent integration?
A common starting point: let a customer connect their own AddEvent account so events created in your product appear on their published calendar. Teams also use it for the other use cases listed above, and expose it to agents for governed reads and writes.
How much does the AddEvent integration cost?
It is included. Pricing is based on connected accounts, not on how many connectors you enable, so adding AddEvent does not change your per-connector cost. You can start free with 3 connected accounts.
Add AddEvent to your product
Start free with 3 connected accounts. No sales call required, and no per-customer integration code.