canonical: https://jentic.com/apis/addevent.com/addevent # AddEvent API Jentic publishes the only available OpenAPI specification for AddEvent API, keeping it validated and agent-ready. AddEvent provides programmatic add-to-calendar buttons, hosted event pages, and RSVP collection for marketers and event organisers. The v2 API exposes calendars and events as first-class resources, with RSVP endpoints for capturing attendee responses and an account endpoint for retrieving the authenticated user's profile. Authentication is a bearer token passed in the Authorization header. ## For AI agents Create calendars and events, generate add-to-calendar links, and collect RSVPs through AddEvent. Used by marketing automation agents to programmatically schedule events that subscribers can add to Google, Apple, or Outlook calendars. ## Scope Does not send invitation emails, manage attendee availability, or handle two-way calendar sync - use for publishing events and generating add-to-calendar links only. ## Capabilities - Create and manage calendars that group related events under a single subscribable feed - Schedule events with start time, end time, location, and rich descriptive copy - Generate add-to-calendar links and embeds for inclusion in emails and landing pages - Capture RSVP responses from attendees and list them per event - Update or cancel events and propagate the change through subscribed calendars - Retrieve the authenticated AddEvent account's profile and quota information ## Use cases ### Webinar add-to-calendar automation Marketers running webinars want every email registrant to land the event in their calendar without manual copy-pasting. POST /events creates the event in AddEvent and returns add-to-calendar URLs for Google, Outlook, Apple, and ICS, which the email tool drops into the confirmation message. The result is fewer no-shows because the event is already on the attendee's calendar. Example prompt: POST /events with title, start, end, timezone 'America/New_York', and description containing the join link, then return the generated add-to-calendar URLs. ### Multi-event marketing calendar Content teams maintain a public calendar of upcoming product launches, AMAs, and office hours that subscribers can follow. POST /calendars creates the calendar feed, and subsequent POST /events calls add entries that appear automatically in every subscriber's app. Updating or deleting an event via PATCH or DELETE /events/{eventId} propagates within minutes. Example prompt: POST /calendars to create 'Product Launches', then POST /events three times to add the next quarter's launch dates. ### RSVP collection for community events Community managers running meetups need accurate attendee counts. GET /events lists scheduled events, and the RSVP endpoints return who has accepted, declined, or marked as maybe. An automation can pull these counts each morning to size catering or send personalised reminders to confirmed attendees. Example prompt: GET /events to find the upcoming meetup, then call the RSVP endpoint for that event ID and count responses by status. ### AI agent event scheduling via Jentic An AI assistant for an event marketing team uses Jentic to call AddEvent when the user says 'create a calendar event for our next webinar'. Jentic returns the POST /events schema, the agent fills the fields from the brief, and the response includes shareable add-to-calendar links the agent pastes back into the chat. The bearer token never enters the agent's context - Jentic injects it at execute time. Example prompt: Use Jentic to search 'create an addevent calendar event', load the POST /events schema, and execute with title, start, end, and timezone for an upcoming webinar. ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | /me | Get current account info | | GET | /calendars | List calendars | | POST | /calendars | Create a calendar | | GET | /events | List events | | POST | /events | Create an event | | PATCH | /events/{eventId} | Update an event | | DELETE | /events/{eventId} | Delete an event | ## Key resources - **Calendars** — Subscribable calendar feeds that group events for a specific audience. - **Events** — Individual scheduled events with title, time, location, description, and add-to-calendar links. - **RSVP** — Attendee responses to events for tracking attendance and reminders. - **Account** — The authenticated AddEvent account profile and quota information. ## Why Jentic - **Setup:** Wiring the AddEvent API by hand means attaching its bearer token in the Authorization header on every call and threading calendar and event ids through publishing endpoints without a published spec. Through Jentic you install once, import the AddEvent API from the API Directory, store the token once, and your agent calls it. - **Permission scoping:** AddEvent puts the event id in the URL path (/events/{eventId}), so a rule can pin your agent to one event: it can patch that event and nothing else. You choose the operations it may call, so deleting events or creating calendars is not included unless you add it. - **Credential handling:** Your AddEvent bearer token is stored once, encrypted, by your own Jentic One instance 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 an event with add-to-calendar links', and Jentic returns the matching AddEvent operation with its input schema so the agent calls the right endpoint without browsing the reference docs, which matters because AddEvent does not publish a public OpenAPI spec. ## Related APIs - **Calendly API** — Scheduling platform that handles availability discovery and booking, not pre-set events. - **Nylas API** — Direct calendar sync API connecting to Google, Microsoft, and IMAP calendars per-user. - **SendGrid API** — Email delivery used to send the calendar invitations or reminders that AddEvent does not. ## FAQ ### Why is there no official OpenAPI spec for AddEvent API? AddEvent does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call AddEvent API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the AddEvent API use? The AddEvent API uses HTTP bearer tokens - a token created in the AddEvent dashboard is sent in the Authorization header. Jentic stores the token encrypted in your Jentic One instance and injects it at execute time so it never enters agent context. ### Can I generate add-to-calendar links with the AddEvent API? Yes. POST /events creates an event and the response includes shareable URLs for Google Calendar, Outlook, Apple Calendar, and a downloadable ICS file. These URLs can be embedded in emails or landing pages directly. ### How do I create an event through Jentic? Search Jentic for 'create an addevent event', load the POST /events schema, and execute with title, start, end, and timezone fields filled. Jentic returns the AddEvent event object including the calendar buttons URL. ### Are there rate limits on the AddEvent API? AddEvent applies per-account rate limits that vary by plan. The spec does not declare a fixed value, so respect any 429 response surfaced through Jentic and back off according to the Retry-After header. ### Does this API send invitation emails to attendees? No. AddEvent provides the calendar event and shareable add-to-calendar links - sending invitations or reminders is left to your email tool of choice (e.g., SendGrid, Mailgun, or your marketing automation system). ### Can I limit what my agent is allowed to do with the AddEvent API? Yes. Because you self-host Jentic One, your own rules decide which AddEvent operations and credentials the agent may use. AddEvent puts the event id in the URL path (PATCH /events/{eventId}), so you can pin the agent to a single event and let it update only that one. Operations you do not grant, such as deleting events or creating calendars with POST /calendars, stay off limits unless you add them.