Indonesian marketplace catalog monitoring
Use Tokopedia endpoints to turn indonesian marketplace catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Turn Tokopedia — Indonesia's largest marketplace, part of the GoTo Group — into structured JSON: keyword search with sorting and filters, category and homepage browsing, full product detail, review-filter metadata, and search-box autocomplete, all with one API key.
Search Tokopedia's product catalog, browse categories and homepage recommendations, and get full public product detail as structured JSON.
Endpoint families
5
Documented params
20
Examples
8
Live catalog snapshot
Active endpoints
8
Methods
GET
Required params
15
Schema refs
8
{
"platform": "Tokopedia",
"endpoint": "tokopedia-search",
"method": "GET",
"path": "/tokopedia/search",
"auth": "apiKey"
}Use cases
Search Tokopedia's product catalog, browse categories and homepage recommendations, and get full public product detail as structured JSON.
Use Tokopedia endpoints to turn indonesian marketplace catalog monitoring into repeatable API requests with documented inputs and JSON responses.
Use Tokopedia endpoints to turn price and assortment tracking into repeatable API requests with documented inputs and JSON responses.
Use Tokopedia endpoints to turn search and homepage merchandising research into repeatable API requests with documented inputs and JSON responses.
Managed execution
Every figure below is read from the live Tokopedia endpoint catalog — 8 endpoints, 20 documented request parameters, and 8 published response schemas — the same catalog Docs and Playground run against.
8 documented Tokopedia endpoints, grouped into 5 request families — Home, Product and Search, plus 2 more.
20 request parameters are documented across those Tokopedia endpoints, 15 of them required — the full input contract is public before you write any integration code.
8 of the 8 Tokopedia endpoints ship a recorded example response, and 8 carry a documented response schema — you can code against the real JSON before the first request.
Tokopedia endpoints document their error responses (400, 404, 429 and 503) alongside the success schema, so a block, a rate limit, or a missing record comes back as a typed error rather than silently empty data.
8 hosted MCP tools back the Tokopedia endpoints, so an agent can call the same routes with the same parameters and the same JSON contract, with no custom glue.
Coverage map
/tokopedia/home/tabs
/tokopedia/product
/tokopedia/search
/tokopedia/autocomplete
/tokopedia/category
Endpoint catalog
/tokopedia/searchReturns public Tokopedia product cards for a keyword from Tokopedia's public product-search operation. `sort` accepts `3` (lowest price), `4` (highest price), `5` (most reviewed), `9` (newest), or `23` (most relevant). Repeat `filter` as `key:value` using values from `/tokopedia/search/filters`.
Sampled 14 Oct 2026: 60 items, 8 fields filled in every item. price: 80,000 to 3,399,000, median 391,200; name: “SALOMON SPEEDCROSS 3 HOLIDAY Unisex Sportstyle Running Shoe…” and 58 other values.
MCP tool tokopedia_search
/tokopedia/search/filtersReturns the live filter tree and supported sort choices for a Tokopedia product search. The response includes categories when the current query exposes them, store type, delivery location, price, rating, offer, condition, recency, shipping, and stock options as applicable.
Sampled 14 Oct 2026: 10 items, 2 fields filled in every item, 3 not. title: “Durasi Pengiriman” and 9 other values; searchable: true in 1 of 1.
MCP tool tokopedia_search_filters
/tokopedia/autocompleteReturns current public Tokopedia search suggestions for a partial keyword. Suggestions include canonical product-search URLs and are not product-search results.
Sampled 14 Oct 2026: 9 items, 3 fields filled in every item. text: “sepatu pria” and 8 other values; url: tokopedia.com.
MCP tool tokopedia_autocomplete
/tokopedia/categoryReturns public product cards from a canonical Tokopedia category path. `path` must begin with `/p/`; use the category page path, not a product or search URL.
Sampled 14 Oct 2026: 5 items, 2 fields filled in every item. name: “Sony SHAKE-X10D Home Audio Speaker Bluetooth With DVD Shake…” and 4 other values; url: tokopedia.com.
MCP tool tokopedia_category
/tokopedia/home/tabsLists the current Tokopedia home recommendation tabs, each with its `id`, `name` and an optional image URL, plus a `fetched_at` timestamp. It takes no parameters. Pass a returned `id` as `tab_id` to `/tokopedia/home` to load that tab.
Sampled 14 Oct 2026: 11 items, 2 fields filled in every item, 1 not. name: “For You” and 10 other values; image_url: p16-images-comn-sg.tokopedia-static.net.
MCP tool tokopedia_home_tabs
/tokopedia/homeReturns public product-card recommendations for a current Tokopedia home tab. Omit `tab_id` for the first available tab; discover other tabs through `/tokopedia/home/tabs`.
Sampled 14 Oct 2026: 19 items, 8 fields filled in every item. price: 21,888 to 400,000, median 97,020; name: “Mieia Panci Presto Rumah Tangga Serbaguna Pengoperasian Sat…” and 18 other values.
MCP tool tokopedia_home
/tokopedia/productReturns public product detail from a canonical Tokopedia shop domain and product key. This endpoint does not accept arbitrary URLs; numeric product IDs are returned when the product page exposes them but cannot be used as lookup input.
Sampled 14 Oct 2026: 11 of 11 fields returned with a value. price: 25,092,000; shop_domain: “ismile-indonesia”.
MCP tool tokopedia_product
/tokopedia/product/review-filtersReturns which public review media, rating, and topic filters are available for a numeric product ID. It does not return review text, review media, or a review archive.
Sampled 14 Oct 2026: 6 items, 2 fields filled in every item. available: true in 6 of 6.
MCP tool tokopedia_product_review_filters
Related APIs
Marketplaces & Retail
Research new, used, and vintage instruments across Reverb listings, seller shops, and the Price Guide. Keep current asking prices separate from historical sales, and preserve model, finish, year, condition, and currency when comparing gear.
Marketplaces & Retail
Collect marketplace product signals from Amazon without building brittle storefront scrapers.
Marketplaces & Retail
Build resale, pricing, and marketplace workflows from structured eBay data.
How to scrape Tokopedia
Crawlora's Tokopedia endpoints return normalized public storefront data as JSON with one API key — no Tokopedia account required.
Send a required q keyword to /tokopedia/search, with optional page (1 through 5), sort (lowest/highest price, most reviewed, newest, or most relevant), and repeated filter key:value pairs. Call /tokopedia/search/filters with the same q first to discover which filter keys and values are currently live for that search.
Pass up to 100 characters of partial product text to /tokopedia/autocomplete for Tokopedia's own search-box suggestions.
Pass a canonical category path beginning with /p/ to /tokopedia/category. For homepage recommendations, call /tokopedia/home/tabs to list the current tabs, then pass a tab_id and page (1 through 5) to /tokopedia/home.
Pass the canonical shop_domain and product_key pair (as returned by search or category results) to /tokopedia/product for full public detail. Use /tokopedia/product/review-filters with a numeric product_id for that product's review-filter metadata.
FAQ
Call /tokopedia/search with a keyword for results, /tokopedia/category with a category path for a category grid, or /tokopedia/product with a shop_domain and product_key for full detail — all return structured JSON with one API key.
/tokopedia/search/filters takes the same q keyword as /tokopedia/search and returns the sort options and filter key:value pairs currently live for that search — pass those values straight back into /tokopedia/search's sort and filter parameters.
/tokopedia/product does not take a raw URL — it takes the canonical shop_domain and product_key pair, both of which /tokopedia/search and /tokopedia/category results already include for each listing.
No — /tokopedia/search, /tokopedia/search/filters, and /tokopedia/category run over a lightweight persisted-request transport with no browser rendering, while /tokopedia/product still renders through Crawlora's browser fleet, matching heavier product-detail endpoints elsewhere in the catalog.
No. Every endpoint reads Tokopedia's own public storefront and requires only your Crawlora API key.