Search Wish products API

Endpoint facts

Method

GET

API path

/wish/search

Auth

apiKey

Credits

3 credits/request

Platform

Wish

Response schema

#/definitions/wish.searchResponseDoc

Overview

Searches Wish's product catalog by keyword, with real offset-based pagination. Returns normalized products with price, currency, rating, review count, and merchant id. A query with no matches returns a normal, empty result rather than an error. Developers commonly use this endpoint for data enrichment, monitoring, research dashboards, internal automation, and agent-native workflows that need repeatable structured public web data. Authentication uses the documented Crawlora headers, and usage is metered with the credit cost shown on this page.

Authentication

Send your scraping API key in the x-api-key header. Use the console API Keys page to rotate or select the active key.

Billing

Endpoint usage is metered in credits. The plan prices, included credits, limits, and overage rates below match the active backend billing configuration.

Credit cost

3 credits/request

Charged response

Successful 2xx responses

Infrastructure behavior

This endpoint is executed through Crawlora's managed scraping infrastructure.

• Proxy strategy: managed automatically where needed
• Browser rendering: enabled for supported targets that require rendered HTML or JavaScript execution
• Browser cluster: supported dynamic workloads can be routed through distributed browser instances
• Retry behavior: automatic retry/fallback may be used depending on endpoint type
• Challenge handling: challenged pages or unusable upstream HTML are detected and surfaced clearly when they cannot be used
• Billing: credits are charged only for successful 2xx responses
• Observability: responses include request context where available

Response behavior

- Pagination is real, but Wish's own backend requires each subsequent page to be requested with the same `count` used on the first page of that sequence -- this endpoint replays that pattern internally, so a nonzero `offset` costs one extra upstream request per page walked. `next_offset` is the offset to request for the next page; `has_more` is `true` while more results remain. An `offset` that is not an exact multiple of `count`, or exceeds the reachable depth for the given `count`, returns `400` before any upstream request is made -- increase `count` to reach deeper pages in fewer steps. - A query with no matches returns a normal `200` with an empty `products` array and `has_more: false`, not an error. - `price` and `currency_code` reflect the requester's own localized pricing (e.g. a Hong Kong-geolocated request sees `HKD` prices); they are not always US dollars. - `rating` and `review_count` reflect the product's current aggregate rating; a brand-new product with no reviews yet returns `0` for both rather than an error. ```json {"code":200,"msg":"OK","data":{"query":"shoes","count":30,"offset":0,"result_count":3,"next_offset":30,"has_more":true,"products":[{"product_id":"68b46c0356ea5dba05e9f755","name":"Waterproof Leather Casual Sneakers for Men, Lightweight Breathable Walking Shoes, Fashion Athletic Running Shoes","price":129.74,"currency_code":"HKD","rating":5,"merchant_id":"68ad644a332a553b38e113ec","image_url":"https://canary.contestimg.wish.com/api/webimage/68b46c0356ea5dba05e9f755-medium.jpg","url":"https://www.wish.com/product/68b46c0356ea5dba05e9f755"}],"source_url":"https://www.wish.com/api/feed/get-search-universal-feed","fetched_at":"2026-08-10T10:00:00Z"}} ```

Error behavior

Crawlora does not silently return bad data when the upstream page cannot be used.

When possible, Crawlora returns structured error context so your integration can retry, back off, or inspect the request.

Related