The event's title. It must be a non-empty, single-line string.

The ID of the calendar that this event will be associated with. Defaults to the default calendar on the account if not provided.

The start date & time of the event. Accepts datetimes in the following formats:

• YYYY-MM-DD hh:mm:ss e.g. 2023-11-28 10:00:00
• YYYY-MM-DD hh:mm e.g. 2023-11-28 10:00
• YYYY-MM-DD e.g. 2023-11-28

The end date & time of the event. Accepts datetimes in the following formats:

• YYYY-MM-DD hh:mm:ss e.g. 2023-11-28 10:00:00
• YYYY-MM-DD hh:mm e.g. 2023-11-28 10:00
• YYYY-MM-DD e.g. 2023-11-28

Defaults to datetime_start + 1 hour if not set.

The event's timezone. This ensures that the event appears at the correct time for users regardless of their timezone.

The List timezones endpoint returns all of the timezone values that are supported, or you can use our Timezone Lookup Tool to find a timezone. Defaults to the calendar's timezone if not provided.

This property also accepts the value floating, which means that the event will appear at the same time in each user's timezone. For example, the event will be at 2 pm local time for users in Paris and 2 pm for local time for users in San Francisco.

The event's recurring rule which must use the iCalendar Standard's format. See our Recurring Rule Generator for help with generating valid recurring rules.

Leave this property empty to create an even that does not repeat.

Please note:

1. Recurring rules are advanced functionality and need to be tested before using them.
2. datetime_start must match the recurring rule to work in strict calendar systems like Outlook (desktop) and Apple Calendar.
3. Recurring rules are not supported by Yahoo Calendar.

The event's description. This field accepts plain text or simplified HTML. Use \n to create a new line. Simplified HTML is not supported by all calendar clients, in which case, the content will be automatically converted into readable text.

Please note: We recommend keeping your description short and to the point, with a maximum of 500 characters. Some browsers (e.g., Microsoft Edge) limit the number of characters that can be transferred in a URL, so this limit ensures that your event is cross-browser compatible.

An internal name for the event which will not be displayed publicly. This can be used internally to distinguish between events, to add additional information/context to an event, or to store an external ID that relates to another system.

The event's location. This can be an address or a URL, for example, a meeting or webinar link. Only one of location and location_id can be provided.

The event organizer's name. If organizer_name is provided, then organizer_email must also be provided. The organizer information is displayed on the event landing page, and including an organizer means the event is considered a meeting by calendar clients such as Outlook (desktop) rather than an appointment.

The event organizer's email address. If organizer_email is provided, then organizer_name must also be provided. The organizer information is displayed on the event landing page, and including an organizer means the event is considered a meeting by calendar clients such as Outlook (desktop) rather than an appointment.

Indicates whether the event appears as free or busy when the user adds it to their calendar. Accepts the following values:

• free: the event appears as free and does not block the user's calendars
• busy: the event appears as busy and blocks the user's calendar
• default: the event uses the user's default free/busy setting

The ID of the custom event landing page template to associate with the event. Accepts the value default, which uses the standard AddEvent template, or the ID of a custom template, which can be retrieved with the List event templates endpoint.

The ID of the custom RSVP form to associate with the event. Accepts the value default, which uses the standard AddEvent template, or the ID of a custom RSVP form, which can be retrieved with the List RSVP forms endpoint.