Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>The links in Dave's post are great. Just to put a few technical details about the google links into an answer here on SO:</p> <p><strong>Google Calendar Link</strong></p> <p><code>&lt;a href="http://www.google.com/calendar/event?action=TEMPLATE&amp;text=Example%20Event&amp;dates=20131124T010000Z/20131124T020000Z&amp;details=Event%20Details%20Here&amp;location=123%20Main%20St%2C%20Example%2C%20NY"&gt;Add to gCal&lt;/a&gt;</code></p> <p>the parameters being:</p> <ul> <li>action=TEMPLATE (required)</li> <li>text (url encoded name of the event)</li> <li>dates (ISO date format, startdate/enddate - must have both start and end time - the button generator will let you leave the endtime blank, but you must have one or it won't work.) <ul> <li>to use the user's timezone: <strong>20131208T160000/20131208T180000</strong> </li> <li>to use global time, convert to UTC, then use <strong>20131208T160000Z/20131208T180000Z</strong></li> <li>all day events, you can use <strong>20131208/20131209</strong> - note that the button generator gets it wrong. You must use the following date as the end date for a one day all day event, or +1 day to whatever you want the end date to be.</li> </ul></li> <li>details (url encoded event description/details)</li> <li>location (url encoded location of the event - make sure it's an address google maps can read easily)</li> </ul> <hr> <h2>Update Feb 2018:</h2> <p>Here's a new link structure that seems to support the new google version of google calendar w/o requiring API interaction:</p> <p><code>https://calendar.google.com/calendar/r/eventedit?text=My+Custom+Event&amp;dates=20180512T230000Z/20180513T030000Z&amp;details=For+details,+link+here:+https://example.com/tickets-43251101208&amp;location=Garage+Boston+-+20+Linden+Street+-+Allston,+MA+02134</code></p> <p>New base url: <code>https://calendar.google.com/calendar/r/eventedit</code></p> <p>New parameters:</p> <ul> <li>text (name of the event)</li> <li>dates (ISO date format, startdate/enddate - <em>must</em> have both start and end time) <ul> <li>an event w/ start/end times: <strong>20131208T160000/20131208T180000</strong> </li> <li>all day events, you can use <strong>20131208/20131209</strong> - <em>end date must be +1 day to whatever you want the end date to be</em>.</li> </ul></li> <li>ctz (<a href="https://en.wikipedia.org/wiki/List_of_tz_database_time_zones" rel="noreferrer">timezone</a> such as America/New_York - leave blank to use the user's default timezone. Highly recommended to include this in almost all situations. For example, a reminder for a video conference: if three people in different timezones clicked this link and set a reminder for their "own" Tuesday at 10:00am, this would not work out well.)</li> <li>details (url encoded event description/details)</li> <li>location (url encoded location of the event - make sure it's an address google maps can read easily)</li> </ul> <p>Notes:</p> <ul> <li>the old url structure above now redirects here</li> <li>supports https</li> <li>deals w/ timezones better</li> <li>accepts <code>+</code> for space in addition to <code>%20</code> (<code>urlencode</code> vs <code>rawurlencode</code> in php - both work)</li> </ul>
    singulars
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload