Errors
HTTP status codes and error bodies from the SearchIn API.
Errors return JSON with a detail string. Validation failures may include an errors array.
{ "detail": "message" }HTTP status codes
| Code | Meaning |
|---|---|
401 | Missing, invalid, disabled, or expired API key. |
403 | Account is banned. |
404 | Search not found or not owned by your account. |
422 | Invalid request body, query validation, or provider / input_type pair. |
502 | Upstream provider or API key verification failure. |
503 | API key verification is not configured on the server. |
422 is usually a catalog mismatch
If POST /v1/search returns 422, the provider does not support that input_type. Call GET /v1/providers or check the pricing matrix.
Search-level failure vs HTTP error
A 200 response can still have status: "failed" or status: "refunded". Those are accepted jobs that did not produce matches — inspect error on the search object. HTTP 4xx/5xx means the request never became a billed search (except where documented otherwise).