Strange error 403: "Calendar usage limits exceeded" when adding event with attendee

[Nir Kornfeld]

Hello,

I'm trying the most simple thing using the API explorer (using this page: )

Request parameters

calendarId

primary

Request body

{
  "summary": "Another test",
  "start": {
    "dateTime": "2017-01-17T11:30:00+02:00"
  },
  "end": {
    "dateTime": "2017-01-17T12:00:00+02:00"
  },
  "attendees": [
    {
      "email": "some_mail@some_domain.com"
    }
  ]
}

But after clicking the Execute button, I get the following error:

{
 "error": {
  "errors": [
   {
    "domain": "usageLimits",
    "reason": "quotaExceeded",
    "message": "Calendar usage limits exceeded."
   }
  ],
  "code": 403,
  "message": "Calendar usage limits exceeded."
 }
}

What am I doing wrong?

[John Boswell]

This isn't anything you are doing wrong. It happens when too many users are trying out the API at the same time. The demo credentials have a limit to their usage. This is usually short-term as this quota resets fairly often.

If this happens very often, please follow up here so we can to look at usage rates and see about tweaking the demo credential's quota. But since currently this is rarely a problem, for now I think it's ok just to wait out the reset or use your own credentials (which will never have this problem unless you overuse the API yourself).

Sorry for the inconvenience and confusion.

[Nir Kornfeld]

Hello John,

Thank you for the answer.

I am sorry, but I think the situation you describe is not the case, and the reasons I think that are:

1. I did use my own credentials, and issue those calls from my C# program. The reason I've used the API Explorer was just a test to see that there is nothing wrong with my code.

2. Even when using the API Explorer, I have no problem at all when adding events without any attendees. The quota error is thrown *only* when I'm adding attendees to the events I'm creating. If what you wrote was true, I would have get the same error whether the events had attendees or not...

I think the API treats events with external (non gmail) attendees differently.

--
You received this message because you are subscribed to a topic in the Google Groups "Google APIs Explorer Users Forum" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/google-apis-explorer-users/C4Qgv-pjKvU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to google-apis-explorer-users+unsub...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[John Boswell]

I'm sorry, I misunderstood when you said "using the API explorer". You are correct that this behavior wouldn't happen like this in your own code or with different parameters.

I am not seeing this issue myself in API Explorer when sharing with other users, including ones outside of the gmail (or any google) domain, so I'm not sure what would be causing it. Without being able to reproduce it, there's not much I can do. But you may have better luck finding someone who knows more about that API specifically by posting on somewhere like StackOverflow.

On Tuesday, January 17, 2017 at 2:45:43 PM UTC-8, Nir Kornfeld wrote:

Hello John,

Thank you for the answer.

I am sorry, but I think the situation you describe is not the case, and the reasons I think that are:

1. I did use my own credentials, and issue those calls from my C# program. The reason I've used the API Explorer was just a test to see that there is nothing wrong with my code.

2. Even when using the API Explorer, I have no problem at all when adding events without any attendees. The quota error is thrown *only* when I'm adding attendees to the events I'm creating. If what you wrote was true, I would have get the same error whether the events had attendees or not...

I think the API treats events with external (non gmail) attendees differently.