Security update: AddEvent is now SOC 2 compliant   →   Read more

Back to Documentation

Events API & Calendar API (AddEvent Calendar & Events API v2)

Build, sync, and manage calendar data with AddEvent’s REST-based Events API and Calendar API v2. Create events, search and retrieve existing events, update or delete them, and manage calendars - all with predictable, resource-oriented endpoints and standard HTTP response codes.

Prefer an interactive explorer? Use the full API reference with “Try it” requests and real-time logs:



Overview

The AddEvent Calendar & Events API v2 (often used as an Events API and Calendar API) lets you programmatically manage calendars and calendar events from your own product, backend, or integrations. The API accepts JSON request bodies and returns JSON responses.

  • Events API: create, search, retrieve, update, and delete events.
  • Calendar API: create, search, retrieve, update, and delete calendars.
  • More resources: RSVP attendees, calendar subscribers, templates, and timezones (in the full reference docs).

Quickstart

Base URL

All endpoints below are under this base URL:

https://api.addevent.com/calevent/v2

Authentication

Authenticate using an API key in the Authorization header with HTTP Bearer authentication:

Authorization: Bearer <apiKey>

For details (and how to find your API key), see: Authentication.

First request (list/search events)

Search returns a result object that includes an events array (up to page_size items). An empty array means “no matches” — still a successful response.

curl --request GET \
  --url https://api.addevent.com/calevent/v2/events \
  --header "accept: application/json" \
  --header "authorization: Bearer <apiKey>"

Endpoints

Events API

Method Path What it does
POST /events Create a new event on an existing calendar
GET /events Search events you’ve previously created (returns an events array)
GET /events/{event_id} Retrieve a single event
PATCH /events/{event_id} Update an event (only provided fields change; others remain unchanged)
DELETE /events/{event_id} Permanently delete an event

Explore the live reference pages: Create event, Search events, Retrieve event, Update event, Delete event.

Calendar API

Method Path What it does
POST /calendars Create a calendar
GET /calendars Search calendars you’ve previously created
GET /calendars/{calendar_id} Retrieve a calendar
PATCH /calendars/{calendar_id} Update a calendar (only provided fields change; others remain unchanged)
DELETE /calendars/{calendar_id} Permanently delete a calendar

Explore the live reference pages: Create calendar, Search calendars, Retrieve calendar, Update calendar, Delete calendar.

Examples (cURL)

Create an event

Creates a new event on an existing calendar. For the full request body fields, see the reference documentation.

curl --request POST \
  --url https://api.addevent.com/calevent/v2/events \
  --header "accept: application/json" \
  --header "content-type: application/json" \
  --header "authorization: Bearer <apiKey>" \
  --data '{
    "calendar_id": "cal_123",
    "title": "Demo event",
    "start": "2026-02-10T10:00:00Z",
    "end": "2026-02-10T10:30:00Z"
  }'

Note: Field names above are illustrative — use the exact schema shown in the endpoint reference.

Retrieve an event

curl --request GET \
  --url https://api.addevent.com/calevent/v2/events/<event_id> \
  --header "accept: application/json" \
  --header "authorization: Bearer <apiKey>"

Update an event

Updates only the provided fields; any fields you omit remain unchanged.

curl --request PATCH \
  --url https://api.addevent.com/calevent/v2/events/<event_id> \
  --header "accept: application/json" \
  --header "content-type: application/json" \
  --header "authorization: Bearer <apiKey>" \
  --data '{
    "title": "Updated demo event"
  }'

Delete an event

curl --request DELETE \
  --url https://api.addevent.com/calevent/v2/events/<event_id> \
  --header "authorization: Bearer <apiKey>"

Create a calendar

curl --request POST \
  --url https://api.addevent.com/calevent/v2/calendars \
  --header "accept: application/json" \
  --header "content-type: application/json" \
  --header "authorization: Bearer <apiKey>" \
  --data '{
    "name": "My product calendar"
  }'

Note: Use the exact schema shown in the endpoint reference.

Errors & response codes

AddEvent uses conventional HTTP response codes (2xx success, 4xx request errors, 5xx server errors). For many 4xx errors, responses include an error_id and a human-readable message.

See the full list and troubleshooting notes: Response codes & errors.

Common use cases for an Events API / Calendar API

  • Sync events from your system: Create and update calendar events from bookings, webinars, or CRM lifecycle changes.
  • Searchable event stores: Query events you’ve created to power dashboards and admin tools.
  • Calendar management: Separate events by customer, team, or product area with multiple calendars.
  • RSVP workflows: Pair the Events API with RSVP resources to collect and manage attendee details (see full reference).

Want no-code automation? Explore: Integrations.


FAQ



What is the difference between the Events API and Calendar API?

The Events API manages event objects (create/search/retrieve/update/delete). The Calendar API manages calendar containers that events live inside.

How do I authenticate to the AddEvent API?

Send your API key as a Bearer token in the Authorization header. Example: Authorization: Bearer .

What’s the base URL for the Calendar & Events API v2?

https://api.addevent.com/calevent/v2

Where can I find the full schema for request/response fields?

Use the interactive AddEvent API reference at docs.addevent.com/reference for full field lists, examples, and a Try It explorer.