Title: &#039;Bad Request&#039; error on widget
Last modified: August 22, 2016

---

# 'Bad Request' error on widget

 *  Resolved [hrachovec](https://wordpress.org/support/users/hrachovec/)
 * (@hrachovec)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/)
 * Hello:
 * Thanks for the plugin. It was working successfully for a few years, but seems
   to have broken recently. I’m getting an error which reads:
 * > An error has occured.
   >  Bad Request No events to display.
 * **Changes I’ve made:**
    – deleted and reinstalled the plugin – created a new 
   feed – double-checked my feed ID was correct in the Widget – double-checked my
   Google Calendar ID was correct – went through the Google API process so that’s
   all authorised
 * Still, no luck.
    The calendar should appear on this page (half way down under
   the ‘Events’ orange bar: [http://gestaltcentre.co.uk](http://gestaltcentre.co.uk)
 * Here’s some screenshots of my settings:
    [https://www.evernote.com/l/AASkhH_IkclPL5U17HwVp7ZDKAALjndk_MQ](https://www.evernote.com/l/AASkhH_IkclPL5U17HwVp7ZDKAALjndk_MQ)
 * Any feedback would be welcome.
 * Cheers, R
 * [https://wordpress.org/plugins/google-calendar-events/](https://wordpress.org/plugins/google-calendar-events/)

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

 *  Plugin Contributor [Nick Young](https://wordpress.org/support/users/nickyoung87/)
 * (@nickyoung87)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544142)
 * Hey sorry you are having issues. I took a look and it looks like there is an 
   issue with your API key. Make sure you follow the process here to get it setup
   correctly:
 * [http://wpdocs.philderksen.com/google-calendar-events/getting-started/api-key-settings/](http://wpdocs.philderksen.com/google-calendar-events/getting-started/api-key-settings/)
 * Thanks!
 *  Thread Starter [hrachovec](https://wordpress.org/support/users/hrachovec/)
 * (@hrachovec)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544210)
 * Hey Nick:
 * Thanks for your quick reply. I went through thew whole API key process again 
   and that seems to have fixed it. Maybe I didn’t copy/paste the entire key before?
   Who knows.
 * Thanks for your help.
 * Kind regards, Russell
 *  Plugin Contributor [Nick Young](https://wordpress.org/support/users/nickyoung87/)
 * (@nickyoung87)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544263)
 * Russell,
 * Great! I am glad that you were able to get it working now. Let us know if you
   have any more questions.
 * Thanks!
 *  [mattslot](https://wordpress.org/support/users/mattslot/)
 * (@mattslot)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544282)
 * I’m getting the same errors as the OP in the widget.
 * The setup document suggests using a server key, but doesn’t the javascript run
   on the clients browsers? It might work for a given host, but not for anyone else.
 *  [aparente001](https://wordpress.org/support/users/aparente001/)
 * (@aparente001)
 * [11 years, 6 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544283)
 * All I know is, if you follow the documentation about the API key, you should 
   be fine. Try it!
 *  [Lonnie](https://wordpress.org/support/users/lonniehb/)
 * (@lonniehb)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544378)
 * One of my calendars stopped working too, it had been fine for a couple years 
   at least.
 * I had to create a new project and API to get it to work again.
 *  Plugin Contributor [Fulvio Notarstefano](https://wordpress.org/support/users/nekojira/)
 * (@nekojira)
 * [10 years, 8 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544379)
 * problem outlined here [https://wordpress.org/support/topic/individual-google-api-keys-now-required?replies=7](https://wordpress.org/support/topic/individual-google-api-keys-now-required?replies=7)
 *  [jazzinjubal](https://wordpress.org/support/users/jazzinjubal/)
 * (@jazzinjubal)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544383)
 * I was getting the “Bad Request” error in the widget and went through the steps
   to create and implement the new API key and am still getting the error. Any thoughts?
 * Widget on right panel.
 * Jason
 * [http://vineyardshreveport.org/](http://vineyardshreveport.org/)
 *  [chriscwcoil](https://wordpress.org/support/users/chriscwcoil/)
 * (@chriscwcoil)
 * [10 years, 7 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544389)
 * I can’t seem to get this to work either. I have double checked all my settings
   in Google Console and the api key. Whenever I include a calendar on my page it
   stops rendering when loading the calendar.

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

The topic ‘'Bad Request' error on widget’ 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/)

## Tags

 * [calendar](https://wordpress.org/support/topic-tag/calendar/)
 * [widget](https://wordpress.org/support/topic-tag/widget/)

 * 9 replies
 * 8 participants
 * Last reply from: [chriscwcoil](https://wordpress.org/support/users/chriscwcoil/)
 * Last activity: [10 years, 7 months ago](https://wordpress.org/support/topic/bad-request-error-on-widget/#post-5544389)
 * Status: resolved