Mercari master API

Endpoint facts

Method

GET

API path

/mercari/master

Auth

apiKey

Credits

1 credit/request

Platform

Mercari

Response schema

#/definitions/mercari.masterResponseDoc

Overview

Returns Mercari's full reference taxonomy in one call: every category (with parent linkage), every recognized brand, and every clothing/shoe/apparel size. Large (tens of thousands of brand entries) and effectively static -- cache this response rather than polling it. Credential-free public data sourced from Mercari's own mobile-app API using an anonymous, login-free session. 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

- This is a large response — tens of thousands of brand entries. It is effectively static day to day; the endpoint is served with a 24-hour edge cache, so repeated calls do not re-fetch from Mercari each time. - `categories` is a flat list with `parent_id` linkage rather than a nested tree, matching the shape Mercari's own data uses. `parent_id` is omitted (zero) for a top-level category (e.g. "Women", "Men", "Home"); `icon_url` is only populated for top-level categories. - `sizes` is one flat list spanning all size-bearing categories — it is not scoped per-category. `short_name` and `code` are the two parts a size's `name` is composed from when both are present (e.g. name `"XS (0-2)"` = short_name `"XS"` + code `"(0-2)"`); either may be absent when Mercari's own data doesn't split them out. Example response (truncated — the real response has ~3,000 categories, ~28,000 brands, and ~380 sizes): ```json { "code": 200, "msg": "OK", "data": { "categories": [ { "id": 1, "name": "Women", "icon_url": "https://u-mercari-images.mercdn.net/assets/img/home_categories/1.png" }, { "id": 11, "name": "Dresses", "parent_id": 1 } ], "brands": [ { "id": 1, "name": "104+ Octane Boost" }, { "id": 4, "name": "3.1 Phillip Lim" } ], "sizes": [ { "id": 1, "name": "XXS (00)", "short_name": "XXS", "code": "(00)" }, { "id": 2, "name": "XS (0-2)", "short_name": "XS", "code": "(0-2)" } ] } } ```

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