Skip to main content

Invalid API Code: Common Causes & How to Fix Them

See what to do if you get an invalid API code when trying to use the extension, and how to quickly fix the most common causes blocking it from working properly.

Rosemary Haddad avatar
Written by Rosemary Haddad
Updated this week

Common Causes & How to Fix Them

1. Ad Blockers or Privacy Extensions

Some ad blockers and privacy tools silently block background requests made by browser extensions.

What you can do:

  • Temporarily disable ad blockers or privacy extensions

  • Try again in an Incognito window with extensions disabled

To enable extensions:

  1. Open Chrome, and click ⋮ at the top of any window or tab.

  2. Click Extensions.

  3. Find the extension you want to allow in Incognito windows.

  4. Click Details under that extension.

  5. Toggle on Allow in Incognito.


2. Corporate Firewall or Managed Work Laptop

If you’re using a company laptop, IT security policies may block unknown domains or restrict browser extensions.

What you can do:

  • Try from a personal computer or a different network (e.g. home Wi-Fi)


3. Chrome Extension Permission Settings

Chrome allows users to restrict when extensions can access websites. If the extension is set to “On click only”, background requests may fail.

Check Extension Permissions

The extension requires specific permissions to function correctly. Here’s how to check:

  • Open Google Chrome

  • Go to the Chrome Extensions page by typing chrome://extensions/ in your browser’s address bar.

  • Locate the extension and click on Details.

  • "Automatically allow access on the following sites" is switched ON. This is 99% times the reason you see sign in button despite being signed in.
    Make sure you have automatically allowed access to all sites.


4. Antivirus or Web Protection Software

Some antivirus tools (e.g. Norton, Kaspersky) intercept or block HTTPS requests to unfamiliar API domains.

What to do:

  • Check if you have antivirus software with web protection enabled

  • Temporarily disable it and test again

Did this answer your question?