Okay so this is really frustrating, Even though I set eventLabelVersion=1, I still cannot see the event labels. Is it not available yet in the API?
I am running into the same issue. This is currently blocking me from accurately determining an event’s color via the API.
When working with eventLabelVersion=1, there are two main requirements that must be met for custom event labels to register and show up properly:
​1. The Parameter Must Be in the Request URL
​It is not enough to just include eventLabelVersion=1 in the payload body or as a standard header depending on the library being used. The API strictly requires it to be appended as a query parameter directly to the request URL:
https://www.googleapis.com/calendar/v3/calendars/calendarId/events?eventLabelVersion=1
If this parameter is omitted or misplaced, the API will fall back to eventLabelVersion=0, which completely ignores the modern eventLabelId property and relies strictly on the legacy colorId.
​2. Labels Must First Be Defined on the Calendar
​Before an event can be assigned a specific label ID (eventLabelId), that label must be explicitly registered within the calendar’s configuration.
​Define the Labels: Use the Calendars.update or Calendars.patch method to add a list of available labels to the calendar’s labelProperties.eventLabels schema. Each label needs an id and a hex backgroundColor. ​Assign the Label: Once the calendar knows that the label ID exists, you can pass that exact eventLabelId in your Events.insert or Events.update payload.
​Note: If an event is updated with an eventLabelId that hasn’t been defined in the calendar’s labelProperties first, the API will fail to resolve or display the label text properly.
Thanks for your response. To clarify, my issue was only observed on reads (writes were ok). But, the problem is resolved now. The API appears to have been updated to include eventLabelIds on read in the last ~week.