Title: Error calling GET
Last modified: April 7, 2017

---

# Error calling GET

 *  [pronesis](https://wordpress.org/support/users/pronesis/)
 * (@pronesis)
 * [9 years, 2 months ago](https://wordpress.org/support/topic/error-calling-get-4/)
 * Hello,
 * I installed and setup up your plugin but when I’m including it into my WP page
   it returns me these rows:
 *     ```
       While trying to retrieve events, Google returned an error:
   
       Error calling GET https://www.googleapis.com/calendar/v3/calendars/7n0rjrnt1etplqqqapdmplf74o%40group.calendar.google.com/events?singleEvents=true&maxResults=2500&timeZone=Europe%2FRome&timeMin=2017-03-08T00%3A00%3A00%2B01%3A00&timeMax=2018-04-06T23%3A59%3A59%2B02%3A00&key=700942803584-220oupvsg53jq4e73uh1bj0srin4c1to.apps.googleusercontent.com: (400) Bad Request
   
       Please ensure that both your Google Calendar ID and API Key are valid and that the Google Calendar you want to display is public.
   
       Only you can see this notice.
       ```
   
 * It seems that your guide about API activation is old compared to the steps I 
   have found now, while setting up my APIs (actually it asks me something related
   OAuth).
    Should I need to configure everything through the account connected 
   with the calendar I want to get? Because I’m doing all for a client of mine and
   I have his calendar public, and so far I used my google account to do everything.
   Please let me know how I can manage this issue, thanks in advance! Emanuele

Viewing 2 replies - 1 through 2 (of 2 total)

 *  Plugin Contributor [Nick Young](https://wordpress.org/support/users/nickyoung87/)
 * (@nickyoung87)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/error-calling-get-4/#post-9067628)
 * I was just informed minutes ago about the API Keys documentation not being up
   to date so I have added that to our list of things to take care of.
 * For the Free version there is not a way to enter oAuth credentials so you need
   to just create the normal API Keys without oAuth.
 * I would recommend doing it under your client’s account just to avoid any possible
   future headaches.
 *  [bdonovanw](https://wordpress.org/support/users/bdonovanw/)
 * (@bdonovanw)
 * [9 years, 1 month ago](https://wordpress.org/support/topic/error-calling-get-4/#post-9071682)
 * Followed the directions on [http://docs.simplecalendar.io/google-api-key/](http://docs.simplecalendar.io/google-api-key/)
   and am getting the same error:
 *     ```
       While trying to retrieve events, Google returned an error:
   
       Error calling GET https://www.googleapis.com/calendar/v3/calendars/Bacil%20Donovan%20Warren%20Public%20Events/events?singleEvents=true&maxResults=2500&timeZone=America%2FPhoenix&timeMin=2017-03-27T00%3A00%3A00-07%3A00&timeMax=2018-04-25T23%3A59%3A59-07%3A00&key=REDACTED: (404) Not Found
   
       Please ensure that both your Google Calendar ID and API Key are valid and that the Google Calendar you want to display is public.
   
       Only you can see this notice.
       ```
   
 * API is setup without referer restrictions—a topic for another day—and is connected
   to a public calendar.

Viewing 2 replies - 1 through 2 (of 2 total)

The topic ‘Error calling GET’ is closed to new replies.

 * ![](https://ps.w.org/google-calendar-events/assets/icon-256x256.png?rev=1263960)
 * [Simple Calendar - Google Calendar Plugin](https://wordpress.org/plugins/google-calendar-events/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/google-calendar-events/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/google-calendar-events/)
 * [Active Topics](https://wordpress.org/support/plugin/google-calendar-events/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/google-calendar-events/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/google-calendar-events/reviews/)

 * 2 replies
 * 2 participants
 * Last reply from: [Nick Young](https://wordpress.org/support/users/nickyoung87/)
 * Last activity: [9 years, 1 month ago](https://wordpress.org/support/topic/error-calling-get-4/#post-9067628)
 * Status: not resolved