Get GOAT curated links API

Endpoint facts

Method

GET

API path

/goat/curated

Auth

apiKey

Credits

1 credit/request

Platform

GOAT

Response schema

#/definitions/goat.curatedResponseDoc

Overview

Returns the shelf of editorially curated links GOAT is currently promoting in its own search box: seasonal collections, specific product searches, and browse-all entry points. Every link is actionable against this API -- a collection link carries a value for GET /goat/collection, a search link carries a query for GET /goat/search. Credential-free public data. 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

1 credit/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

- **Every link is actionable against this API.** A `collection` link's `collection_slug` goes to `GET /goat/collection` (or `GET /goat/search`'s `collection_slug`); a `search` link's `query` goes to `GET /goat/search`'s `query`. - `collection_slug` carries GOAT's own identifier, and **not every value resolves.** Readable slugs such as `back-to-school-2026` work on `GET /goat/collection` (verified 2026-09-07: 470 products). GOAT also emits bare numeric internal ids (e.g. `31841`) in the same field, and those return **no results** on `GET /goat/collection` — they are an internal id space that endpoint does not accept. Check whether the value is numeric before following it, and expect an empty collection if you pass one through anyway. - `browse` links are catch-all shelves ("Shop All Items") described by a `filter_key`/`filter_value` pair from GOAT's own merchandising config. They have no direct equivalent parameter on `GET /goat/search`; use an unfiltered search to browse the whole catalog instead. - The shelf is editorial and rotates — it reflects what GOAT is promoting at request time, so treat neither its size nor its contents as stable. Example response (truncated for brevity): ```json { "code": 200, "msg": "OK", "data": { "links": [ { "title": "Back To School", "type": "collection", "collection_slug": "back-to-school-2026" }, { "title": "Awake NY x Air Jordan 6", "type": "search", "query": "Awake NY x Air Jordan 6" }, { "title": "Shop All Items", "type": "browse", "filter_key": "group_id", "filter_value": "all" } ], "total": 10 } } ```

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