Google Calendar Web

broken image


  1. Features. Displays a preview of your calendar while you're navigating. (works on any page.). If you're on certain sites where it detects the presence of events, the icon changes to an orange '+'. Clicking that icon lets you add the event to your Google Calendar, and shows you a map (if there's a location it could detect.).
  2. Get the official Google Calendar app for your Android phone and tablet to save time and make the most of every day. Different ways to view your calendar - Quickly switch between month, week and day view. Events from Gmail - Flight, hotel, concert, restaurant reservations and more are added to your calendar automatically. Tasks - Create, manage, and view your tasks alongside.
  3. By importing a snapshot of your Google calendar into Outlook, you can see it alongside other calendars in the Outlook Calendar View. To keep the imported calendar up-to-date, subscribe to the Google Calendar in Outlook. If you don't, the only way to update it will be to import another, more current snapshot.

Every request your application sends to the Google Calendar API must include an authorization token. The token also identifies your application to Google.

About authorization protocols

Google is updating Calendar on the web with basic offline viewing functionality. This joins Gmail, Drive, and Docs/Sheets/Slides, though the new feature is currently only for Google Workspace.

Your application must use OAuth 2.0 to authorize requests. No other authorization protocols are supported. If your application uses Google Sign-In, some aspects of authorization are handled for you.

Authorizing requests with OAuth 2.0

Google Calendar Com

All requests to the Google Calendar API must be authorized by an authenticated user.

The details of the authorization process, or 'flow,' for OAuth 2.0 vary somewhat depending on what kind of application you're writing. The following general process applies to all application types:

  1. When you create your application, you register it using the Google API Console. Google then provides information you'll need later, such as a client ID and a client secret.
  2. Activate the Google Calendar API in the Google API Console. (If the API isn't listed in the API Console, then skip this step.)
  3. When your application needs access to user data, it asks Google for a particular scope of access.
  4. Google displays a consent screen to the user, asking them to authorize your application to request some of their data.
  5. If the user approves, then Google gives your application a short-lived access token.
  6. Your application requests user data, attaching the access token to the request.
  7. If Google determines that your request and the token are valid, it returns the requested data.

Some flows include additional steps, such as using refresh tokens to acquire new access tokens. For detailed information about flows for various types of applications, see Google's OAuth 2.0 documentation.

Here's the OAuth 2.0 scope information for the Google Calendar API:

ScopeMeaning
https://www.googleapis.com/auth/calendarread/write access to Calendars
https://www.googleapis.com/auth/calendar.readonlyread-only access to Calendars
https://www.googleapis.com/auth/calendar.eventsread/write access to Events
https://www.googleapis.com/auth/calendar.events.readonlyread-only access to Events
https://www.googleapis.com/auth/calendar.settings.readonlyread-only access to Settings
https://www.googleapis.com/auth/calendar.addons.executerun as a Calendar add-on

To request access using OAuth 2.0, your application needs the scope information, as well asinformation that Google supplies when you register your application (such as the client ID and theclient secret).

Google Calendar Web Application

Google calendar webhook

Google Calendar Web Portal

Tip: The Google APIs client libraries can handle some of the authorization process for you. They are available for a variety of programming languages; check the page with libraries and samples for more details.

Perform Google Workspace Domain-Wide Delegation of Authority

In enterprise applications you may want to programmatically access users data without any manual authorization on their part. In Google Workspace domains, the domain administrator can grant to third party applications domain-wide access to its users' data—this is referred as domain-wide delegation of authority. To delegate authority this way, domain administrators can use service accounts with OAuth 2.0.

For additional detailed information, see Using OAuth 2.0 for Server to Server Applications





broken image