This method allows users to create CoveritLive events on the fly. Events can be created simply by specifying just a title and start date / time, or additional parameters can be included for finer-grained control of the event particulars. This method returns the event code if the event is successfully created, allowing for further interactions through the API.
API Rate Limited:
true (no more than 500 events created in a 24 hour period)
In addition to the parameters listed in the Request Parameters section, the event/create method also includes the following parameters:
The title of the event to be created. May not be > than 90 characters in length.
Indicates whether the event to be created is a ticker. Set this parameter to 'y' to denote that the event is a ticker.
Defines the general category of the event. Correctly categorizing your event makes it easier for Readers to find and potentially increases your live event traffic. Possible values include:
The scheduled start date of the event, in the following format:
If no timezone is provided, this date defaults to the timezone provided in the user account which is denoted by the token parameter. For upcoming events that have a Title Page, this date (along with the scheduled start time) will be displayed to viewers.
The scheduled start time of the event, in 24 hour format:
HH:MM (24-hour format of an hour without leading zeros:minutes with leading zeros). MM must be one of 00, 15, 30, 45 (ie, only 15 minute start time increments are allowed).
For upcoming events that have a Title Page, this time (along with the scheduled start date) will be displayed to viewers.
The timezone that the event falls into, represented as a decimal number. The scheduled_startdate and scheduled_starttime parameters are assumed to be in this timezone. If not provided, it defaults to the timezone provided in the user account which is denoted by the token parameter. Possible values include:
(GMT -12:00) Eniwetok, Kwajalein
(GMT -11:00) Midway Island, Samoa
(GMT -10:00) Hawaii
(GMT -9:00) Alaska
(GMT -8:00) Pacific Time (US & Canada)
(GMT -7:00) Mountain Time (US & Canada)
(GMT -6:00) Central Time (US & Canada)
(GMT -5:00) Eastern Time (US & Canada), Bogota, Lima
(GMT -4:00) Atlantic Time (Canada), Caracas, La Paz
(GMT -3:30) Newfoundland
(GMT -3:00) Brazil, Buenos Aires, Georgetown
(GMT -2:00) Mid-Atlantic
(GMT -1:00 hour) Azores, Cape Verde Islands
(GMT) Western Europe Time, London, Lisbon, Casablanca
(GMT +1:00 hour) Brussels, Copenhagen, Madrid, Paris
(GMT +2:00) Kaliningrad, South Africa
(GMT +3:00) Baghdad, Riyadh, Moscow, St. Petersburg
The web address of the event. This address will be included in any shared Facebook and Twitter links, on event email invites, reader reminders and in the Live Now Listings. It's important to provide the correct public location as this address is used to drive traffic back to your live event.
*Note - if you do not wish to share the event location, make it private by including the private request parameter and setting its value to 'y'
Indicate whether an event is private. Facebook and Twitter sharing is disabled for private events. Private events do not appear in the Live Now Listings, and the email reminder is hidden for Upcoming private events. The location request parameter is not required for private events.
y - event is private
n - event is not private
Explicitly set the template that will be used for the viewer window for the event. The template id value can be retrieved using the template/list method. IF not specified, the template for the event is set to the default template for the user.
If the event to be created is not private, a tweet will be published to the CiLEvents Twitter account when the event is started. This tweet will contain the title and location of the event, as well as any additional text contained in the tweet_text parameter (space permitting). May not exceed 140 characters in length.
Indicate whether an event should have a title page. By default the Viewer Window includes a built in Title Page (also referred to as a "Veil"). The Title Page displays your event title, event status, and main image. It is particularly useful for displaying custom branding. Readers click the Title Page to view your live event. If disabled the Title Page will no longer appear for Live Events and Replays.
y - event has titlepage
n - event does not have titlepage
Allow your live event Readers to submit comments and images via email. All submitted items can be previewed from the Console. Defaults to disabled if not specified.
y - email comments enabled
n - email comments disabled
Allow your live event Readers to attach images to their comments. All submitted images can be previewed from your Console, and published at your discretion. This option is not available when Reader Comments have been turned off (check your template settings). Reader comments and attachments can also be managed from your Writer's Console. Defaults to enabled if not specified.
y - reader attachments enabled
n - reader attachments disabled
If this parameter is set to 'y', your Live Event can be found and watched by any Reader browsing the CoveritLive "Live Now" Listings. Private events do not appear in Live Listings. If private request parameter is included and set to 'y', the show_live_listings parameter is ignored.
y - event will appear in live listings
n - event will not appear in live listings
If this parameter is set to 'y', CoveritLive will provide three RSS feeds for your readers at the bottom of your Viewer Window:
Live event: The RSS feed will display every published entry from a specific event
Writer: The RSS feed will display a listing and links to every upcoming, live and completed event from that CiL username
Groups: For Group members; the RSS feed will display a listing and links for all upcoming, live and completed events from all writers within the Group
y - rss is enabled for the event
n - rss is disabled for the event
This option turns avatars on for all event Writers / Contributors. Avatars appear next to the posted comment.
y - writer avatars enabled
n - writer avatars disabled
When Reader Login Options are enabled, this option allows you to control Reader avatar display. When enabled, the Reader's associated avatar will appear beside their published comment.
y - reader avatars enabled
n - reader avatars disabled
The event code of a successfully created event is returned in the data field of a general response. This field will consist of an event_code field, which contains the event code.
Example response to a successful event/create request:
CoveritLive is the leading live-event publishing platform. Since its release in 2007, CoveritLive has been used by thousands of writers to engage millions of readers around the world. It is actively used both by traditional bloggers, journalists, major brands and mainstream media.