Pristine Marketplace Search API

Endpoint facts

Method

GET

API path

/pristine-marketplace/search

Auth

apiKey

Credits

3 credits/request

Platform

PristineMarketplace

Response schema

#/definitions/shopifybrands.siteSearchResponseDoc

Overview

Returns normalized products from Pristine Marketplace's (https://www.pristinemarketplace.com) own native full-text search results page, distinct from `/pristine-marketplace/search/suggest`'s predictive suggestions. The storefront URL is fixed server-side. Per-page size is fixed by the storefront's own theme (16 products per page) and is not adjustable; `limit` is honored only as an upper bound on the returned page. 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

- `total_count` reflects the storefront's own true result count (parsed from the results page's own title, e.g. "413 results found for jordan"), not just the count on this page. - A genuine no-match query returns `200` with an empty `products` array. This is distinguished from parser drift using the page's own "No results found for ..." status marker; zero product cards without that marker present is treated as an upstream error instead of a silent empty success. - Every returned product's `available` is currently always `true`: broad live sampling (~48 cards across multiple search queries) found no sold-out item in this storefront's search results at all, suggesting sold-out items are excluded from search results entirely rather than shown as unavailable. - Blocked pages, malformed HTML, and missing product-card markup (with no empty-state marker) return upstream errors. Example response: ```json { "code": 200, "msg": "OK", "data": { "store_url": "https://www.pristinemarketplace.com", "source_url": "https://www.pristinemarketplace.com/search?q=jordan&type=product", "query": "jordan", "page": 1, "limit": 16, "total_count": 413, "total_pages": 26, "products": [ { "handle": "bulls-michael-jordan-signed-nike-air-jordan-v-size-13-shoes-w-original-box-bas", "title": "Bulls Michael Jordan Signed Nike Air Jordan V Size 13 Shoes w/ Original Box BAS", "url": "https://www.pristinemarketplace.com/products/bulls-michael-jordan-signed-nike-air-jordan-v-size-13-shoes-w-original-box-bas", "price": 26999, "available": true } ] } } ```

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