Microsoft_Calendar

Handle Initialize Authorization

post

Handle integration initialization request.

Body
or
Responses
chevron-right
200

Successful Response

application/json
Responseany
post
/connectors/microsoft_calendar/integrations

No content

Handle User Has Integration

get

Handle user integration existence check.

Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/microsoft_calendar/integration-exists
200

Successful Response

No content

Auth Schema

get

Handle authentication schema request.

Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/microsoft_calendar/auth-schema
200

Successful Response

No content

Get Integration

get
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/microsoft_calendar/integrations/{user_identifier}

No content

Select Integration

post
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
post
/connectors/microsoft_calendar/integrations/{user_identifier}

No content

Remove Integration

delete
Path parameters
user_identifierstringRequired
Responses
chevron-right
200

Successful Response

application/json
Responseany
delete
/connectors/microsoft_calendar/integrations/{user_identifier}

No content

Success Authorize Callback

get
Responses
chevron-right
200

Successful Response

application/json
Responseany
get
/connectors/microsoft_calendar/success-authorize-callback
200

Successful Response

No content

Update Event

post

Update the properties of an existing event. Can modify subject, attendees, times, location, body, importance, reminders, online meeting settings, and other event properties. Use PATCH to update only specified fields while preserving others.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
bodyany ofOptional

Event properties to update. Only include fields you want to change.

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/update_event

Delete Event

post

Delete a specific event from the calendar. If the event is a meeting, deleting it on the organizer's calendar sends a cancellation message to all attendees. This action cannot be undone.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/delete_event

Permanent Delete Event

post

Permanently delete an event and place it in the purges folder in the dumpster. Unlike regular delete, this action moves the event to a deeper deletion state that cannot be recovered by standard means. Email clients cannot access permanently deleted items.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/permanent_delete_event

List Calendars

post

Get all the user's calendars. This retrieves calendars from the default calendar group and allows filtering, sorting, and selecting specific properties using OData query parameters.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for customizing the calendar list

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/list_calendars

Create Calendar

post

Create a new calendar for the user. This creates a calendar in the user's default calendar group with the specified name and optional properties like color.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/create_calendar

Get Calendar

post

Get the properties and relationships of a specific calendar object by its ID. This retrieves detailed information about a calendar including permissions, settings, and metadata.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for customizing the calendar details

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/get_calendar

Update Calendar

post

Update the properties of an existing calendar object. You can modify the calendar name, color theme, or default calendar status. Only include properties you want to update.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/update_calendar

Delete Calendar

post

Delete a calendar other than the default calendar. This permanently removes the calendar and all its events. The default calendar cannot be deleted.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/delete_calendar

List Calendar View

post

Get events, occurrences, exceptions and single instances from a calendar within a specified time range. This returns actual calendar events/appointments between the start and end dates.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/list_calendar_view

List Events

post

Retrieve a list of all events in a calendar without date restrictions. This returns single instance meetings, series masters, and recurring events. Use this to get all events in a calendar regardless of time range.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for customizing the event list

or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/list_events

Create Event

post

Create a new event in a calendar. This allows creating meetings, appointments, and events with attendees, locations, recurrence patterns, and online meeting details.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/create_event

Get Schedule

post

Get the free/busy availability information for a collection of users, distribution lists, or resources (rooms or equipment) for a specified time period. Perfect for finding available meeting times and checking when people are free.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/get_schedule

List All Events

post

Get a comprehensive list of all event objects across all calendars in the user's mailbox. This provides a unified view of all events from every calendar, supporting timezone preferences and OData query parameters for filtering, sorting, and pagination. Complements the specific calendar LIST_EVENTS function.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for customizing the event list

or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/list_all_events

Create Event Default

post

Create an event in the user's default calendar with simplified parameters. Perfect for quick event creation without specifying a calendar ID. Supports all event features including attendees, locations, recurrence patterns, and online meeting details.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/create_event_default

Get Event

post

Get the properties and relationships of a specific event. Returns event details including subject, body, attendees, location, start/end times, and all other event properties. Supports timezone preferences and custom property selection.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for customizing the event response

or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/get_event

Delta Events

post

Get a set of event resources that have been added, deleted, or updated in a calendarView (a range of events defined by start and end dates) of the user's primary calendar. Supports delta query for incremental sync.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
queryany ofOptional

Query parameters for delta sync. Specify startDateTime and endDateTime for the initial call. Use $deltatoken or $skiptoken for subsequent calls.

or
nullOptional
headerany ofOptional

Optional request headers for customizing the response

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/delta_events

Forward Event

post

Forward a meeting event to new recipients. Allows the organizer or attendee to forward the meeting request, optionally including a comment. The new recipients will be added to the event and notified.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/forward_event

Accept Event

post

Accept the specified event in a user calendar. Optionally include a comment and choose whether to send a response to the organizer.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
bodyany ofOptional

Request body for accepting the event.

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/accept_event

Tentatively Accept Event

post

Tentatively accept the specified event in a user calendar. Optionally include a comment, propose a new time, and choose whether to send a response to the organizer.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
bodyany ofOptional

Request body for tentatively accepting the event.

or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/tentatively_accept_event

Dismiss Reminder

post

Dismiss a reminder that has been triggered for an event in a user calendar.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/dismiss_reminder

Snooze Reminder

post

Postpone a reminder for an event in a user calendar until a new time.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/snooze_reminder

List Instances

post

Get the instances (occurrences) of an event for a specified time range. If the event is a seriesMaster, returns the occurrences and exceptions in the range.

Body
response_fieldsany ofOptional

List of dot-notation field paths to include in the response. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use: Specify field paths using dot notation to include only those fields in the response. Supports nested fields (e.g., 'user.name', 'payload.headers'). When filtering lists, each item is filtered recursively. If a top-level field is specified without sub-fields, the entire value is included. If nested fields are specified, only those nested fields are included.

Example: ["id","name","status"]
string[]Optional
or
nullOptional
response_filtersany ofOptional

Filters to apply to response items. This is a post-processing filter that does not alter the data request nor the 3rd party response data.

How to use:

  • field_name: The field to filter on. Supports dot notation for nested fields (e.g., 'creator.age'). When filtering list items, this filters the items themselves. When using root, this filters elements within the array at the root path.
  • root: Optional path to an array of dictionaries. When set, filters the array elements at this path instead of filtering the items themselves. Use dot notation (e.g., 'payload.headers'). Important: The root path must target an array of dictionaries (the last array before filtering by field_name value), and field_name should be a field within those dictionary elements. In nested array structures, root should point to the final array of dictionaries that contain the field_name field. Otherwise no filtering will occur.
Example: [{"field_name":"status","type":"string_list","values":["open","in_progress"]}]
or
nullOptional
Responses
chevron-right
200

Successful Response

application/json
post
/connectors/microsoft_calendar/list_instances

Last updated