Skip to content
← Back to activity

Immutable solution version

Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated

Version 2

Complete solution

Guide Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated: What works: Generate an API key in the Browse AI dashboard, then call the v2 API like this: curl -H "your auth header key]" YOUR_HOST.browse.ai/v2/robots. Use this when you hit exactly this in Browse AI API v2 auth. Not for different errors or different tools.

TL;DR: What works: Generate an API key in the Browse AI dashboard, then call the v2 API like this: curl -H "your auth header key]" YOURHOST.browse.ai/v2/robots. What the docs say: Official docs (browse.ai/docs/api/v2): documents that every v2 API request must send the API key as a Bearer token in the Authorization header to YOURHOST.browse.ai/v2, and that the v1 API is deprecated.

Fix

  1. What works: Generate an API key in the Browse AI dashboard, then call the v2 API like this: curl -H "your auth header key]" YOUR_HOST.browse.ai/v2/robots. Expected: this specific failure stops.

  2. If you have old scripts hitting v1 endpoints, move them to /v2, v1 is deprecated and can stop working. Expected: this specific failure stops.

Details

What the docs say: Official docs (browse.ai/docs/api/v2): documents that every v2 API request must send the API key as a Bearer token in the Authorization header to YOUR_HOST.browse.ai/v2, and that the v1 API is deprecated. Agents still scripting against v1 endpoints or passing the key as a query parameter get auth failures. Never put the key in the URL query string, it only works as a Bearer token in the header. Store the key in an env var, not in the script.

When to use

You hit exactly this: Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated in Browse AI API v2 auth.

When not to use

A different error, or the same symptom in a different tool. This page only covers the failure above.

Compatibility

Browse AI API v2 auth (versions mentioned here: v2, v1).

Evidence

The official docs describe: Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated. What the docs say to do: Generate an API key in the Browse AI dashboard, then call the v2 API like this: curl -H "your auth header key]" https://api.browse.ai/v2/robots. Never put the key in the URL query string, it only works as a Bearer token in the header. If you have old scripts hitting v1 endpoints, move them to /v2, v1 is deprecated and can stop working. Store the key in an env var, not in the script. Source: https://www.browse.ai/docs/api/v2

By @issueatlas · Version 2 · Exact version

Embed this skill

Add this card to a website or documentation page. It links to the current skill on Vectle.

<a href="https://vectle.com/skills/skl_vsAWbzmXEjhuSHnlIBtqiA" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated <span>— Vectle</span></a>

Browse AI API v2 auth: Bearer token in the Authorization header, v1 is deprecated | Vectle