Receiving error: message: 'Calendar usage limits exceeded.' with new project with attendees in event object

1
votes

I am receiving an error,

Calendar usage limits exceeded

When trying to insert an event into a new calendar.

The Attempt is showing up in the API dashboard so I know the credentials are correct.

I have ensured billing is attached, and I have added the service account to the google calendar.

Not sure what else can be adjusted on this, any ideas what else could be causing this error? It says in my quotas that I can do up to 1 million requests, I have done under 50... EDIT: I have discovered that the removal of the attendees from the event object allows the event to insert.

2
node.jsapigoogle-apigoogle-calendar-api
@Peter API issues are valid questions on SO there are loads of quota questions and set up of credential questions. – DaImTo
Hello! Could you provide a a sanitized version of your request body? Thanks! – ZektorH
Hi Michael, I've been experiencing the exact same thing. With no attendees, I can insert, but with even one attendee on one event, the event insert fails (403) with a "Calendar usage limits exceeded" message. I have similarly made only a handful of requests. I'm using a service account with Owner permissions, and have tried with attendee emails both inside and outside my org. I have also tried setting sendUpdates: 'none' on the insert request, but it doesn't help. Thanks! – Teg Grenager

2 Answers

0
votes

There are several types of quotas.

enter image description here

Project based quotas: these are the quotas that define what the full project can do. Your project can make 1 million requests a day.

There are also user based quotas these tend to be related to flood protection a user can max make say 500 requests a second.

There are also write quotas. A user can max for example insert 50 events per day.

Project based quotas can be increased user based quotas can not. Write quotas can not be increased. Wait until midnight west coast usa time and the quota will reset.

0
votes

There is an open issue with Google issue tracker for this.

Sorry to not be able to offer more help!