Hi, perry.

If you are using a private Spreadsheet in this situation;

a private sheet does not have to be published to the Web  if the Google Sheets API is implemented,

but that sheet has to be shared with the account with which the API connection is being made.

Please try this :

Unpublish this sheet,  then go to "Share" in the top right corner,

and try to share it with the account which you used to setup the API.

As it has been explained with instructions on this Documentation page.

Let me know if that helped. Thank you

Hi, perry.

Firstly, I would like to sincerely apologize for the delayed response as we have been experiencing an unusually high number of tickets. I am sorry that it has taken longer than usual to respond to your concern and your patience is highly appreciated.

-

I will have to ask our senior 2nd level Team what might be the best way to tackle this issue,

to be honest, i am not sure how much we can help from our end, because this is an error coming from the Google API itself and our plugin only provides the error message.

If you wish to still try what you can from your end, i found this useful help page from Google that explains possible API errors and what you can do to resolve them.

There is only one error with the text "Bad Request", error 400, here is the link for more details about it :

https://developers.google.com/calendar/api/guides/errors#400_bad_request

As soon as our senior Team advises what we might try next from our end, i will report back right away.

Let me know if you resolve this in the meantime.

Thank you.

 Hi, perry.

Actually, what i can try is, 

to connect my Google API credentials with your Plugin Google API settings and see if i get the same error, 

to at least determine with certainty if the plugin functionality works as it should be on your site with our plugin.

Please provide me a temporary WP-admin (administrator) user for your site where this happens, so we could log in and take a look ‘from the inside’ as that’s the most efficient way to see and resolve the issue. 

We do not interfere with any data or anything else except for the plugin (in case that’s a production version of the site); of course, we do not provide login data to third parties. 

You can write credentials here check PRIVATE Reply so nobody can see them except us.