# Why does Nylas require full Google Calendar scope when using primary keyword?

**URL:** <https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012>\
**Category:** Question and Answers\
**Tags:** calendar-api\
**Created:** [December 8, 2025, 10:14am UTC](https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012 "2025-12-08T10:14:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Faizan](https://avatars.discourse-cdn.com/v4/letter/f/f0a364/32.png) [@Faizan](https://forums.nylas.com/u/Faizan)\
**Post date:** [December 8, 2025, 10:14am UTC](https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012/1 "2025-12-08T10:14:36Z")

</div>

Hi team,  
We are trying to fetch Google Calendar events through Nylas using the `primary` keyword as described in the docs ([https://developer.nylas.com/docs/dev-guide/scopes/](https://developer.nylas.com/docs/dev-guide/scopes/)).

Google allows accessing events from the primary calendar using only:

`https://www.googleapis.com/auth/calendar.events.readonly`

But Nylas requires the broader:

`https://www.googleapis.com/auth/calendar`

in order to use the `primary` keyword.

**Question:**  
Why does Nylas require the full calendar scope specifically when using the `primary` keyword, even though Google’s own API allows primary calendar event access with the `calendar.events.readonly` scope?

---

<div class="post-metadata">

**Author:** ![Samuelpx](https://avatars.discourse-cdn.com/v4/letter/s/f04885/32.png) [@Samuelpx](https://forums.nylas.com/u/Samuelpx)\
**Post date:** [December 8, 2025, 10:28am UTC](https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012/2 "2025-12-08T10:28:20Z")

</div>

Hello, Faizan!

the `primary` query parameter requires the reading of calendar attributes, and that requires the specific `https://www.googleapis.com/auth/calendar` scope. SInce all you’re doing with `https://www.googleapis.com/auth/calendar.events.readonly` is reading events (objects) from the calendar, these are actually two distinct operations.

I hope that helped!

Thank you,–Sam Xavier,  
Support Engineer, Nylas

---

<div class="post-metadata">

**Author:** ![Faizan](https://avatars.discourse-cdn.com/v4/letter/f/f0a364/32.png) [@Faizan](https://forums.nylas.com/u/Faizan)\
**Post date:** [December 8, 2025, 11:16am UTC](https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012/3 "2025-12-08T11:16:18Z")

</div>

@Samuelpx  
Thanks for the quick response!!

Currently we are using google’s native calendar APIs to read the calendar events and it’s working fine when the `primary` calendarId is used to fetch the events with the only the `https://www.googleapis.com/auth/calendar.events.readonly` scope.

However, when we try to do the same with Nylas we need to have broader scope. Here are the code snippets for better clarity

When Using Nylas:  
`return this.nylasClient.events.list({`  
` identifier: grantId,`  
` queryParams: {`  
` calendarId: 'primary',`  
` start: startTime.toString(),`  
` end: endTime.toString(),`  
` limit,`  
` ...(pageToken && { pageToken }),`  
` },`  
` });`

When using Google API:

`const googleEventParams = {`  
` calendarId: 'primary',`  
` timeMax: endTime,`  
` timeMin: startTime,`  
` timeZone: 'UTC',`  
` maxResults: 2500,`  
` orderBy: 'startTime',`  
` singleEvents: true,`  
` };`  
`//the above googleEventParams is used to fetch calendar events using google's calendar api `

---

<div class="post-metadata">

**Author:** ![Samuel.R](https://avatars.discourse-cdn.com/v4/letter/s/6bbea6/32.png) [@Samuel.R](https://forums.nylas.com/u/Samuel.R)\
**Post date:** [December 8, 2025, 1:57pm UTC](https://forums.nylas.com/t/why-does-nylas-require-full-google-calendar-scope-when-using-primary-keyword/1012/4 "2025-12-08T13:57:52Z")

</div>

Hello,

When you use `calendarId: 'primary'` with Nylas, Nylas makes an additional API call to resolve “primary” to the actual calendar ID before fetching events. This resolution call hits a different Google API endpoint that requires broader scopes.

Many thanks,  
Samuel R.  
Support Engineer, Nylas
