Back to Troubleshooting Guides

400 redirect_uri_mismatch Error

This guide applies to:

  • Basic Edition
  • Plus Edition
  • Pro Edition
  • Business Edition

Introduction

In this guide, we want to give you some tips on solving the 400 redirect_uri_mismatch error you may get when setting up your Google Calendars sync connection.

This is an error that comes up in the final step of adding the Client ID and Secret to SSA.

This happens when the URL to your site is not typed precisely in the API console to the newly created Client ID and Secret.

This is not your fault; Google is quite picky with the URL. In fact, a trailing slash can cause this error.

Resolving 400 Redirect_uri_mismatch

First, you’ll need to head over to the API console.

To get there, go to https://console.developers.google.com

  1. Make sure you’re on the right project; check in the top-left corner.
  2. Go to the Credentials tab and click on the Oauth Client Id you created.
  3. We will be focused on the Authorized redirect URIs section.
Finding the Authorized Redirect URIs in the Credentials.

Adding the URL

Try adding the exact URL for your site. When you’re done, you can select Save and try again.

If that doesn’t help, please try the next solution of testing out a variety of URLs

Error 400:Redirect_uri_mismatch error when trying to connect to Google Calendar.

Entering a Variety of URLs

As we mentioned above, Google is quite picky with the URL. In fact, a trailing slash can cause this error.

So, let’s enter various URLs into the Authorized Redirect URIs section. Feel free to add every variation of your URL under the Authorized Redirect URIs section.

Enter the following URLs –

  • trailing slash vs. no trailing slash:
    • https://yoursite.com/
    • https://yoursite.com
  • www vs. no www:
    • https://www.yoursite.com
    • https://yoursite.com

When you’re done adding the variety of URIs from above, please Save and try again.

Authorized redirect URIs entered in.

We also have an alternative way of connecting to Google Calendar, using the Quick Connect method, which doesn’t utilize the API.

Still stuck?

File a support ticket with our five-star support team to get more help.

File a ticket

  • Please provide any information that will be helpful in helping you get your issue fixed. What have you tried already? What results did you expect? What did you get instead?
  • This field is for validation purposes and should be left unchanged.

Related Guides