> Portal Navigation:
> 
> - Append `.md` to any URL under `https://dev.wix.com/docs/` to get its markdown version.
> - Pages are either content pages (article or reference text) or menu pages (a list of links to child pages).
> - To get a menu page, truncate any URL to a parent path and append `.md` (e.g. `https://dev.wix.com/docs/sdk.md`, `https://dev.wix.com/docs/sdk/core-modules.md`).
> - Top-level index of all portals: https://dev.wix.com/docs/llms.txt
> - Full concatenated docs: https://dev.wix.com/docs/llms-full.txt

## Resource: Introduction

## Article: Introduction

## Article Link: https://dev.wix.com/docs/api-reference/business-management/calendar/events-v3/introduction.md

## Article Content:

# About the Events API

The Events API lets you manage calendar entries for a
[schedule](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md).
Events inherit [default values](https://dev.wix.com/docs/rest/business-management/calendar/default-values.md)
from their schedule, ensuring consistency across related events. However, you
can override each event's default values as needed.

To set up [recurring events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/recurring-events.md),
define an event with `recurrencePattern` - known as the `MASTER` event. Then,
`INSTANCE` events that hold details for each occurrence are automatically created
based on this pattern.

With the Events API, you can:

+ Create and update single-occurrence and `MASTER` events.
+ Create `EXCEPTION` events by updating an `INSTANCE` event.
+ Retrieve events.
+ Cancel events.
+ Track in real-time when an event is created or modified.

For more in-depth event management, see:

+ [Schedules API](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md)
+ [Events View API](https://dev.wix.com/docs/rest/business-management/calendar/event-views-v3/introduction.md)
+ [Participations API](https://dev.wix.com/docs/rest/business-management/calendar/participations-v3/introduction.md)
+ [Bookings APIs](https://dev.wix.com/docs/rest/business-solutions/bookings/about-wix-bookings.md)

## Before you begin

It’s important to note the following points before starting to code:

+ An event must belong to exactly one schedule.
+ You can't create instances of recurring events. Instead, Wix Calendars automatically
  creates `INSTANCE` events when you set a `recurrenceRule` in the `MASTER` event.
+ Currently, you can define recurrence patterns based only on weeks. For example,
  every week or every 3 weeks. You can't define recurrence rules based on days,
  months, or years yet.
+ To schedule a recurring event on multiple days of the week, you must currently
  define separate `MASTER` events. For example, if an event recurs on Mondays,
  Wednesdays, and Fridays, you need to set up 3 distinct `MASTER` events.
+ You can't directly create exceptions for recurring events. When you update an
  `INSTANCE` event, Wix Calendars automatically changes its `recurrenceType` to
  `EXCEPTION`.
+ By default, `WORKING_HOURS` events aren't returned in [Query Events](https://dev.wix.com/docs/rest/business-management/calendar/events-v3/query-events.md).
+ You can't directly manage `participants` on an event. Use the
  [Participations API](https://dev.wix.com/docs/rest/business-management/calendar/participations-v3/introduction.md)
  to do so.

## Use cases

+ [Manage a calendar](https://dev.wix.com/docs/rest/business-management/calendar/sample-flows.md#manage-a-calendar).
+ [Sync calendars to an external system](https://dev.wix.com/docs/rest/business-management/calendar/sample-flows.md#sync-calendars-to-an-external-system).

## Terminology

+ **Event**: A calendar entry that includes details such as timing, location,
  and participants. Each event is associated with a schedule and can inherit
  [default values](https://dev.wix.com/docs/rest/business-management/calendar/default-values.md).
  Events can be standalone or part of a recurring series. They can block time
  or allow concurrent scheduling on the calendar.
+ **Recurrence type**: Information about whether the event is a single occurrence,
  defines a recurring series, or is part of a recurring series.
  + **`NONE`**: An event that takes place only once. Single-occurrence events
    don't include a `recurrenceRule`.
  + **`MASTER` event**: Defines the recurrence pattern for a series of recurring events.
  + **`INSTANCE` event**: A specific occurrence within a recurring series. You can't
    directly create an event with `{"recurrenceType": "INSTANCE"}`, instead it's
    automatically generated based on the recurrence rule. When you update an
    `INSTANCE`, it automatically changes to an `EXCEPTION`.
  + **`EXCEPTION` event**: A modified instance within a recurring series. For
    example, an event with a different time or location. Exceptions are created
    automatically when you modify an `INSTANCE` event.
+ **Role**: You can assign permissions to [Wix users](https://dev.wix.com/docs/build-apps/develop-your-app/access/about-identities.md#wix-users)
  to control their access to an event. For more details, see the
  [permissions article](https://dev.wix.com/docs/rest/business-management/calendar/permissions.md#roles-for-events).
  + **Writer**: Can read and modify the event.
  + **Commenter**: Can read the event and modify the event `notes`.
+ **Status**: Indicates whether an event can be updated or if it’s permanently
  `CANCELLED`.
+ **Type**: Specifies whether the event adds `WORKING_HOURS` to a
  [schedule](https://dev.wix.com/docs/rest/business-management/calendar/schedules-v3/introduction.md).
  [Bookings APIs](https://dev.wix.com/docs/rest/business-solutions/bookings/about-wix-bookings.md)
  also use this field to indicate if the event is an `APPOINTMENT`, `CLASS`, or `COURSE`.

@sdk_package_setup