POST /api/brave/images/search
Price: 20 credits
Brave image search by query. Returns images with the full-size image url and dimensions, thumbnail, title, the page that hosts the image and its domain. Supports region and safe search filters.
Brave Images results for a query; image is the full-size file and url the page that hosts it. Use count for how many, country for the region and safesearch to filter adult content.
access-token string requiredtimeout integer — Max scrapping execution timeout (in seconds) (default: 300; min: 20; max: 1500)q string required — Search query (examples: "openai"; minLength: 1)country string — Region of the search results (default: "all"; one of: "all", "us", "ar", "au", "at", "be", "br", "ca", "cl", "cn", "de", "dk", "fi", "fr", "gr", "hk", "in", "id", "it", "jp", "kr", "my", "mx", "nl", "nz", "no", "ph", "pl", "pt", "ru", "sa", "sg", "za", "es", "se", "ch", "tw", "tr", "gb")count integer required — Maximum number of images to return (min: 1; max: 200)safesearch string — Adult content filtering level (default: "moderate"; one of: "off", "moderate", "strict")@type string (default: "BraveImage")url string requiredposition integer nullabletitle string (default: "")image string nullablewidth integer nullableheight integer nullablethumbnail string nullablethumbnail_width integer nullablethumbnail_height integer nullabledomain string nullablefavicon string nullablefetched_at integer nullableconfidence string nullable422 — The request body did not validate Check the fields against this schema. A URN with the wrong prefix is the most common cause.408 — The request ran past its time limit Raise `timeout` in the request body, up to the maximum this endpoint documents. Lowering `count` or turning off the `with_*` flags also helps, because less work finishes sooner.412 — The entity was not found, or a precondition failed Retrying will not help: either the entity does not exist, or the input points at a different one.429 — Too many requests: a rate limit or a usage window is exhausted When the response carries an X-Retry-After header, wait that many seconds and retry: the same number is in the body as `detail.retry_after`, and the limit clears once that window passes. The message in the body names the limit that was hit.500 — Something broke on our side Retrying will not help. If it keeps happening, send us the X-Request-ID from the response headers.529 — Rate limit reached, or the endpoint is overloaded Wait at least 30 seconds, then retry.X-Error — Error message text (present only on error)X-Request-ID — Unique request identifierX-Execution-Time — Execution time in secondsX-Result-Count — How many records the body carries. 0 means an empty result, which is a normal answer and not by itself an error. A non-zero count can come back together with X-Error when the failure happened partway through — read this header and X-Error independently.X-Total-Available-Results — How many records exist for this query, when the endpoint can say. On a `dry_run` request this is the answer and the body is empty. It saturates: the endpoint's documented maximum means 'at least that many', any smaller number is exact.X-Warning — Present when the request body carried keys this endpoint does not document. They were ignored, so any filter you meant to apply through them did not apply. Check the spelling against this schema and retry.X-Retry-After — Seconds to wait before retrying. Present only on 429.