AddEvent API

Name: AddEvent API
Brand: AddEvent API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentProductivityCalendar Schedulingbearer13 EndpointsREST

For 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.

Install Jentic One Beta

Connect the AddEvent API to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the AddEvent API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.

Step 1: Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Step 2: Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with AddEvent API.

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

GET STARTED

Start building with AddEvent API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use AddEvent API for, with concrete tasks.

★ 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.

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.

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.

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.

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

13 endpoints — jentic publishes the only available openapi specification for addevent api, keeping it validated and agent-ready.

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

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

Why Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

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.

Intent-based discovery

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.

Time to first call

FAQs

Specific to using AddEvent API through Jentic.

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.

AddEvent API

Connect the AddEvent API to your agent

Capabilities

Start building with AddEvent API

Use Cases

Key Endpoints

Why Jentic?

Related APIs

FAQs