The calendar ID you are wanting to pull in new subscribers from.

Title of the event. Single line string.

Start date of the event. Accepts most date/time formats, e.g. 08/31/2021 03:00 PM (12-hour format) or 31-08-2021 15:00 (24-hour format).

Use numeric values to describe the date, e.g. 08/31/2021 and not textual, e.g. August 31st, 2021.

Dates in the m/d/y or d-m-y formats are disambiguated by looking at the separator between the various components: if the separator is a slash (/), then the American m/d/y is assumed; whereas if the separator is a dash (-) or a dot (.), then the European d-m-y format is assumed. If, however, the year is given in a two digit format and the separator is a dash (-, the date string is parsed as y-m-d. To avoid potential ambiguity, it's best to use ISO 8601 (YYYY-MM-DD) dates

Date examples: 08/31/2021 03:00 PM or 31-08-2021 15:00 or 2021/08/31 03:00 PM or 2021-08-31 15:00

End date of the event. Accepts most date/time formats, e.g. 08/31/2021 05:00 PM (12-hour format) or 31-08-2021 17:00 (24-hour format). Use numeric values to describe the date, e.g. 08/31/2021 and not textual, e.g. August 31st, 2021.

Dates in the m/d/y or d-m-y formats are disambiguated by looking at the separator between the various components: if the separator is a slash (/), then the American m/d/y is assumed; whereas if the separator is a dash (-) or a dot (.), then the European d-m-y format is assumed. If, however, the year is given in a two digit format and the separator is a dash (-, the date string is parsed as y-m-d. To avoid potential ambiguity, it's best to use ISO 8601 (YYYY-MM-DD) dates

Date examples: 08/31/2021 03:00 PM or 31-08-2021 15:00 or 2021/08/31 03:00 PM or 2021-08-31 15:00

Duration of the event in minutes, e.g. "30". Ignores the end date if set and adds the minutes to the start date.

Description of the event. Use an HTML line break tag or \n to separate lines.

The field accepts plain text or simplified HTML. Simplified HTML is supported by calendar clients like Outlook and Apple Calendar. If the calendar client does accept HTML, the content of the field is automatically converted into readable text.

Keep the description short and to the point. Link to a website for further details if the event description is long. Maximum 500 characters recommended.

Reason: Most modern browsers allow an unlimited number of characters to be transferred by the browser. Internet Explorer / Edge only allows ~2000 characters. A 500 characters maximum is recommended to make sure your event is cross browser compatible.

Event location, eg. "Eiffel Tower, Paris".

Event organizer, e.g. "John Johnson".

If you fill out organizer you must also include the organizer_email field.

If you include an organizer and an organizer_email, the event is considered to be a "meeting" by calendar clients like Outlook. If you don't include the fields, the event is considered to be an "appointment".

Event organizer e-mail, e.g. "your@email.com".

If you fill out organizer_email you must also include the organizer field.

If you include an organizer and an organizer_email, the event is considered to be a "meeting" by calendar clients like Outlook. If you don't include the fields, the event is considered to be an "appointment".

All day event. Accepts true or false.

The format of the date in start and end. Accepts the values MM/DD/YYYY or DD/MM/YYYY only. Lets the engine know how to handle the date, e.g. 12-hour format (MM/DD/YYYY) or 24-hour format (DD/MM/YYYY).

The date_format used to be mandatory but is optional today.

The events time zone, e.g. Europe/Paris or America/Los_Angeles.

If timezone is applied (recommended), date/time will be converted to Zulu time / GMT / UTC. If timezone is not applied, date/time will be parsed as is (fluid date/time).

Explanation: The timezone parameter makes sure the date/time is correct no matter if you are in New York or Sydney. If your event has users from multiple time zones in the world, it's highly recommended to use the parameter.

Value to keep track of events. Used for statistics. E.g. "iPhone" or "Newsletter Oct 2016" or URL reference.

Id of a "Custom Event Page" template, e.g. "lm2015e14o720j11". Uses the "AddEvent default" template if template is not defined. In order to create/access custom templates please go to "Events" -> "New Event" and save it. Then scroll down the page and click the "Custom template" button. With "Custom templates" you can edit all HTML of the event page, change date formats (e.g. 24-hour clock) etc.

Event reminder. Trigger an event reminder e.g. "15" minutes before the event starts. Accepted input: Number

Example: Reminder "15" minutes before event starts = 15 or one day before event starts : 60 minutes x 24 hours = 1440.

Event reminders are currently supported by:

• Apple Calendar
• Google Calendar (using Google Events API)
• Outlook
• Outlook.com (using Microsoft Events API)

Recurring rule, e.g. FREQ=WEEKLY;UNTIL=20211110T080000Z;BYDAY=WE,TH,FR Make the event repeat for a number of times.

Recurring rules are advanced and needs to be tested before you publish it. Please notice: The start date/time must match the recurrence rule in order to work in strict calendar systems like Outlook and Apple Calendar.

Recurring rules are currently supported by:

• Apple Calendar
• Google Calendar (using "Direct" and Google Events API)
• Office 365 (using the Microsoft Events API)
• Outlook
• Outlook.com (using Microsoft Events API)

Custom filenaming of the .ics file used for e.g. Outlook and Apple Calendar. If not defined the name defaults to "event.ics". Use the phrase use-title to use the title from the title parameter or enter a custom filename.

Add one or multiple attendees (pre-populated) to the event. Enables the pre-populated attendee(s) to get a response from the attendee. Separate multiple attendees (email addresses) with a comma.

Examples: joe@example.com or joe@example.com,jack@example.com

Id of the event you are wanting to delete.

The email address you're wanting to lookup.

Title of the event. Single line string.

Name of the event. Use for internal purpose only.

Description of the event.

Location of the event, e.g. "1600 Amphitheatre Pkwy, Mountain View, CA 94043".

Event organizer for this event.

Event organizer e-mail.

Start date of the event. Accepts most date/time formats.

End date of the event. Accepts most date/time formats.

The events time zone, e.g. Europe/Paris or America/Los_Angeles.

All day event. Accepts true or false.

Event reminder. Trigger an event reminder e.g. "15" minutes before the event starts.

Recurring rule, e.g. FREQ=WEEKLY;UNTIL=20211110T080000Z;BYDAY=WE,TH,FR

ID of a "Custom Event Page" template, e.g. "a238bkd038dkO". Uses the "AddEvent default" template if template_id is not defined.

Whether the event requires RSVP or not. Optional. Accepts true or false.

ID of the RSVP template to use. Optional. If no template ID is specified the event uses the "Standard RSVP template".

Allows you to save a JSON string containing keys and values which can be used with a custom event templates. E.g. {"name":"Michael","bannerimage":"url-to-image"}

Color of the event as pre-defined in the calendar settings. Accepts 1 to 20.

Id of the event you want to update.

Title of the event. Single line string.

Name of the event. Use for internal purpose only.

Description of the event.

Location of the event, e.g. "1600 Amphitheatre Pkwy, Mountain View, CA 94043".

Event organizer for this event.

If you fill out organizer_email you must also include the organizer field.

Start date of the event. Accepts most date/time formats.

End date of the event. Accepts most date/time formats.

The events time zone, e.g. Europe/Paris or America/Los_Angeles.

All day event. Accepts true or false.

Event reminder. Trigger an event reminder e.g. "15" minutes before the event starts.

Recurring rule, e.g. FREQ=WEEKLY;UNTIL=20211110T080000Z;BYDAY=WE,TH,FR

ID of a "Custom Event Page" template, e.g. "a238bkd038dkO". Uses the "AddEvent default" template if template_id is not defined.

Whether the event requires RSVP or not. Optional. Accepts true or false.

ID of the RSVP template to use. Optional. If no template ID is specified the event uses the "Standard RSVP template".

Allows you to save a JSON string containing keys and values which can be used with a custom event templates. E.g. {"name":"Michael","bannerimage":"url-to-image"}

Color of the event as pre-defined in the calendar settings. Accepts 1 to 20.

Id of the event you are wanting to view.

Limits the results based on a keyword. Performs a wildcard search in these event fields: Title of the event, Internal name of the event, Description of the event, Location of the event

Example: &search=Hello+World"