The redirect URI (where the response is returned to) has to be registered in the APIs console, and the error is indicating that you haven’t done that, or haven’t done it correctly.
Go to the console for your project and look under API Access. You should see your client ID & client secret there, along with a list of redirect URIs. If the URI you want isn’t listed, click edit settings and add the URI to the list.
Updating the google api console and that change being present can take some time. Generally only a few minutes but sometimes it seems longer.
Add Authorised redirect URIs
- Go to the official website of Google Developer Console.
- Select an existing project for whose credentials you added to the plugin settings page.
- Click on the menu icon and find APIs and services hover over this menu and you will see other options now click on Credentials.
- Now click on your OAuth 2.0 Client ID.
- Check if your Authorised redirect URIs section has the same redirect URI from the Google API Settings of the plugin settings page or not.
- If it’s not there then copy the redirect URI from the plugin Google API Settings page and paste it into the project’s Authorised redirect URIs section.
- Save the settings.
It may take five minutes to a few hours for settings to take effect.
Tags
FAQs
post-5083
How do I resolve the Google OAuth 2 authorization Error: redirect_uri_mismatch?
You need to register the redirect URI in the Google APIs console under API Access.
Where can I find my client ID and client secret for Google OAuth 2 authorization?
How long does it take for changes made in the Google API console to take effect?
How do I add Authorised redirect URIs for Google OAuth 2 authorization?
Powered by WPFAQBlock.com
Last updated on July 7th, 2026
