Installing Apidog Chrome Extension

The Apidog Chrome Extension enables you to use Apidog directly in your browser, providing API testing and debugging capabilities without installing the desktop client. However, browser security policies impose certain restrictions that you should be aware of.

Browser Extension Limitations and Solutions

Browser security policies impose certain restrictions on extensions, limiting their functionality in specific scenarios. Below are the key limitations and their workarounds.

Restrictions in Browser Extensions

Forbidden Request Headers

Some headers, such as Cookie, Host, Origin, Content-Length are automatically blocked by browsers. (View the full list here.)

Cookie Limitations

Cross-origin requests will be blocked from carrying cookies unless CORS credentials support is configured

Browser extensions cannot directly read or manipulate cookies (including automatically attaching cookies to requests)

Special Request Types

GET/HEAD methods cannot include a request body, and local code/database calls are restricted

Alternative Solutions

✅ Use Apidog Desktop Client (No restrictions)
✅ Enable Cloud Agent (Bypasses browser limitations)

Installation Guide

Visit the Chrome Web Store page

Click Add to Chrome

Permission Configuration (Required in Some Cases)

If a request fails, you may need to manually allow the extension to access specific permissions:

Go to chrome://extensions and find the Apidog extension

Click Details and under the Permissions, add:

http://apidog.com/*
http://app.apidog.com/*
https://apidog.com/*
https://app.apidog.com/*

FAQs

Why can't certain headers be sent?

Browsers automatically block certain headers (e.g., Cookie). To bypass this, use the Apidog Desktop Client or configure the Cloud Agent.

Why does a cross-origin request return 403/Forbidden?

Check if the server explicitly rejected the request (e.g., authentication failure, IP restrictions)

Configure CORS Proxy

Verify if the backend has CORS headers configured, for example:

Why is the GET request body removed?

Browser standards prohibit GET and HEAD requests from containing a body. Use POST instead or switch to the desktop client for debugging.

Need to call local code/database?

Browser sandboxing does not support this. You need to use the Apidog Desktop Client.

Learn More

CORS Proxy

Request proxy in Apidog web

Request proxy in shared docs

Request proxy in Apidog client

Installing Apidog Chrome Extension

Browser Extension Limitations and Solutions#

Restrictions in Browser Extensions#

Alternative Solutions#

Installation Guide#

Permission Configuration (Required in Some Cases)#

FAQs#