Request Proxy in Shared Docs

When sharing an API documentation or making it public, you can choose a request proxy for the online documentations to avoid cross-origin (CORS) issues.

Available Request Proxies

Request Proxy	Description
Cloud Agent	Uses Apidog's cloud agent to handle requests. Note that this Agent cannot access endpoints from the intranet.
Browser Extension	Uses the browser extension installed by the user in their own browser as the Agent to send requests. If the user has not installed the extension, they will be prompted to install it to initiate requests.
No Proxy	Does not use a cross-origin proxy, meaning requests are sent directly from the user's browser to the endpoint. Ensure that the endpoint server is properly configured to avoid CORS (Cross-Origin Resource Sharing) issues.
Self-hosted request proxy Agent	Uses a self-hosted request proxy agent deployed by your team to handle requests.

📷 Visual Reference

TIP

For public documentation, consider using the Cloud Agent for the best user experience, as it requires no installation. For internal documentation, a self-hosted proxy agent provides better security and access to private networks.

Request Proxy in Shared Docs

Available Request Proxies#

Available Request Proxies