Unable to find information at https://developers.google.com/calendar/v3/reference
Solution
Unfortunaltely, at the moment of this answer there is no available feature for retrieving the working hours throughout the API.
However, you could use the Freebusy query to retrieve the calendar hours you will be busy as a workaround for getting the working hours (you then can of course filter the response data to just get the working hours and not any other busy moment you are not interested in.
Moreover, if you would like to request this feature for Google Calendar API, you can file a feature request in the Public Issue Tracker.
I hope this has helped you. Let me know if you need anything else or if you did not understood something. :)
Related
I've been using Google Calendar API for several years for a project and suddenly I received the following error when requesting the list of holiday events:
(es.mexican#holiday#group.v.calendar.google.com): "Invalid Credentials".
According to the docs, it should be still be possible to authenticate with API Key but when testing it returns the same error. Am I missing something?
It seems to be a bug that affected many users in the last days
I recommend you to give it a "star" to increase visibility and hope for prompt fixing.
I'm trying to write a Zap which will get events from a Google Calendar for the current week and generate a string describing when I'm in the office "Mon, Wed, Fri". The only thing that's stumping me is step 0. How do I auth for the Google Calendar API in a Zapier Code block? It appears that Google calendar only supports Oauth2.0 and only gives out short-lived tokens but I want this scheduled job to only run in the background and have no recourse for user-interaction. Is there any way to generate a long-lived access token?
David here, from the Zapier Platform team.
Unfortunately, that's not something that's easily doable. Part of what Zapier does for you is refresh the tokens and ensure everything is running as expected. Searching for a bunch of data (this week's events) isn't really in the zapier wheelhouse at this time.
If you're only concerned with new events, you could set up a "new event" trigger that adds the date of the event into Storage and a second zap that runs weekly, reads storage, figures out what dates are busy, and generates your string. That wouldn't hold up for recurring events though, so it may not be what you're looking for.
Alternatively, you could try and do the refresh loop in your code block, but that's really tough. You'd need somewhere to persist the token (while Storage technically works, it's open to the public so it's not a great place to store creds, even if they are hard to find). You could try your request, refresh if the token is stale, then send the eventually present value onto a later step.
Sorry I don't have better news. Let me know if you've got any other questions!
We are doing an integration with Google Calendar Api, trying to publish events in a calendar, and then add them to the invited users (attendees) in their primary calendars. After doing a couple of tests and publications we skip the error message:
Calendar usage limits exceeded. [403]
We have read the documentation and the limits of petitions, but we are not passing at any time of that limit, and we skip the same error. We have seen in forums and in the same documentation of the API, that the reasons can be diverse, like the publication of more than 25 calendars, overcome the 10,000 events, etc.
In our case, we do not overcome any of those limitations. To get an idea, we did not surpass the 200 events in a couple of days. And since we started testing, events don't exceed 500. That is why we are trying to contact you as the last solution, because we do not know where the problem is.
Is there are any daily or sendings attendees exact limits ? Because we need to launch and update many of them, and don't know how to do it. How can we publish and share this events without having the limitation failure? In our Google Console we say that the quota still remain 1.000.000 queries per day.
To make myself understood, my procedure is: I have a general Calendar with a Json Keys, and I publish all my events in it. Then, I trying to add attendees and publish(share) part of my events with them. But I have the same error for days. I know that Google Calendar limits the number of invitations a user can send to external guests 100-300 guests exactly. But I do not know if is a limit per hours, days, or account? How we can do to publish many events with attendees without limits? Is there a solution for that?
As can be read in this post, besides what is written in the documentation itself, this is a hard limitation from Google to stop spammers.
Currently there is no real solution and it's up to Google. There are rumors that Google is trying to tackle this issue but nothing has changed in the mean time.
Basically, your only option is either to wait and see what Google does with this or abandon their solution and find an alternative.
When trying to open Google Analytics: User flow under Audience I get the following error. I have been seeing it for the last week and not sure what is going wrong.
One or more of the services on which we depend is unavailable. Please try again later after the service has had a chance to recover.
This feature was working before and I am wondering what went wrong. Thank you. :)
This is a Google-side error. It should clear up with no adjustments on your part, but it's impossible to say how long or what the exact issue is.
I am trying to subscribe to an iCloud calendar on my Google calendar. I am really open to any methods, but here is the one that seems most likely to work. See instructions to build proxy calendar. The problems is that when I try to subscribe to this proxy calendar (using both webdav://... and _http://...), I get the error message "Settings Error--Could not fetch the url." I know the file should work because I was able to use it in Outlook. Any idea on how to fix this, or a completely different alternative that I have not found?
So, the problem fixed itself the next day. I assume this is because Google cached the error and was not going to bother fetching the calendar again. So I guess this was a non-issue.