I’m trying to build a web app that connects to Google Calendar API but keep running into issues. I followed the setup process and created all the necessary credentials. My authorized JavaScript origins are set to http://localhost:3000 for local development.
The app loads fine at localhost:3000/calendar.html and shows the basic interface. When I click the login button, the authentication flow works and I can grant permissions to my Google account. But after that, no calendar data appears on the page.
Looking at the browser console, I see these errors:
GET https://www.googleapis.com/calendar/v3/calendars/primary/events?maxResults=25&orderBy=startTime&showDeleted=false&singleEvents=true&timeMin=2017-08-11T15%3A45%3A12.298Z 403 ()
And also:
Uncaught {"error":{"errors":[{"domain":"usageLimits","reason":"accessNotConfigured","message":"Access Not Configured. Calendar API has not been used in project 558901234567 before or it is disabled. Enable it by visiting console.developers.google.com then retry."}],"code":403,"message":"Access Not Configured"}}
The error message suggests visiting the Google Cloud Console to enable the API, but when I go there it says I don’t have permission to access the calendar API for this project. How can I fix this permissions issue?
That 403 error is super common with Google APIs. It’s telling you the Calendar API isn’t enabled for your project.
Here’s the fix:
Go to Google Cloud Console
Select your project (ID 558901234567)
Hit APIs & Services > Library
Search “Google Calendar API”
Click it and enable
If you’re getting permission errors, double-check you’re logged in with the account that created the project or that you’ve got the right IAM roles.
Honestly though, I got so tired of dealing with Google API setup and permission nightmares that I switched to using Latenode for calendar stuff. No more wrestling with OAuth flows, API credentials, or rate limits.
Latenode connects to Google Calendar without any auth code or API key management. It handles OAuth automatically and gives you a clean interface to read events, create appointments, or sync with other apps.
I’ve built several calendar workflows this way and it’s way cleaner than maintaining custom API integrations. No more 403 errors or credential headaches.
This happens when your project config gets out of sync. I hit the same issue switching between Google accounts during development. Your console shows project ID 558901234567 - make sure Calendar API is enabled for that exact project.
What fixed it for me: completely clear your browser’s Google auth cache. Auth tokens sometimes get stuck pointing to the wrong project or have stale permissions. Log out of all Google accounts, clear cookies for googleapis.com, then redo the auth flow.
Also check if you created OAuth credentials under a personal account but you’re enabling APIs under a different org account. Project ownership gets messy with multiple Google accounts signed in. Use incognito mode and sign in with just the account that owns the project to verify everything matches up.
That permission error usually means you’re logged into Google Console with the wrong account. I’ve hit this exact issue when juggling multiple Google accounts in my browser. Check you’re using the same Google account that created project 558901234567 - Chrome loves to auto-switch accounts and suddenly you’re trying to edit someone else’s project. If that’s not it, your project might be under a Google Workspace where only admins can enable APIs. I’ve seen this at companies before - you’ll need to contact your workspace admin. Last thing - if you just created the project, billing might not be set up. Google wants billing info even for free tier stuff. Hit the billing section and make sure there’s a payment method attached.
The error’s clear - Calendar API isn’t enabled for your project. But here’s what catches people: you need to use the same Google Cloud project in your code as where you enable the API.
Check your credentials’ client ID - it should match that project number in the error (558901234567).
I’ve seen devs create credentials in one project but enable APIs in another. That’s usually why you get permission denied when trying to enable it.
Go to console.cloud.google.com, switch to the right project with the dropdown, then hit APIs & Services > Enabled APIs. Click “+ ENABLE APIS AND SERVICES” and search Calendar API.
Still can’t enable it? Your organization might restrict API access. Happened at my last company - IT locked down what APIs we could enable.
Also check your OAuth consent screen. Sometimes the API enables fine but you get 403s because the consent screen’s missing required fields or stuck in testing mode with wrong test users.
After enabling, wait a few minutes before testing. Google’s systems need time to propagate changes.
had this exact issue last week - drove me crazy for hours. the error message is misleading. you probably have the calendar api enabled, but your oauth2 credentials are wrong. double check that the client id in your javascript matches the one from google cloud console. also make sure you’re using web application credentials, not desktop app ones. i made that mistake and got the same 403 error even though everything looked right.