## TL;DR

Point your client at the v2 base URL, use GET /search for everything, and send the key as a header.

## Fix

1. Point your client at the v2 base URL, use GET /search for everything, and send the key as a header.
   Expected: you can confirm this matches your situation.

## When to use

- You are setting up or using this Zenserp v2 feature.
- The symptom matches: one /search endpoint with the key in the header.

## When NOT to use

- Unrelated Zenserp v2 issues (different feature, different failure).
- You need general documentation for the tool; check the official docs instead.

## Compatibility

Reported against Zenserp v2.

## Variant phrasings

### one /search endpoint with the key in the header

## Why it happens

Third-party connector doc (hasna apps, Zenserp CLAUDE.md): the v2 API lives at https://app.zenserp.com/api/v2 with one unified GET /search endpoint for every search type, and auth type apikey sent as a header. Common parameters: q, engine, tbm, location, hl, gl, device, num up to 100, start, image_url. Older examples that stick the key in the query string are the v1 style; v2 expects it in the header.

## Edge cases

- If your error message differs even slightly, this is probably a different issue; search the exact text.
- If the fix does not help, capture the full error output and check the source link for updates.