Lazada category listing · Lazada API

GET https://api.api.sh/lazada/v1/category

1 credit / call e-commerce try it in the playground →

Products of one Lazada category (Singapore, Malaysia, Thailand, Philippines, Vietnam or Indonesia): name, price, discount, rating, review count, seller, location, image and link, with the sort options and filters the page offers. Pass next_page back as page; it is null on the last page. Every response includes credits_used: the credits this call cost.

Parameters

name	type	description
`category`required	string	Category slug from a Lazada category link (for example shop-laptops), or the link itself. Example: `shop-laptops`
`country`	sg \| my \| th \| ph \| vn \| id	Lazada site: sg (default), my, th, ph, vn, id. Example: `sg`
`sort`	popularity \| price_asc \| price_desc	popularity (default), price_asc or price_desc.
`min_price`	integer	Lowest price, whole units of the local currency.
`max_price`	integer	Highest price, whole units of the local currency.
`page`	integer	Page number. Pass `next_page` from the previous response; it is null on the last page.

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/lazada/v1/category?category=shop-laptops" \
  -H "x-api-key: $APISH_KEY"

import os, requests

res = requests.get(
    "https://api.api.sh/lazada/v1/category",
    params={"category": "shop-laptops"},
    headers={"x-api-key": os.environ["APISH_KEY"]},
    timeout=120,
)
res.raise_for_status()
data = res.json()

const url = new URL("https://api.api.sh/lazada/v1/category");
url.searchParams.set("category", "shop-laptops");

const res = await fetch(url, { headers: { "x-api-key": process.env.APISH_KEY } });
if (!res.ok) throw new Error(`${res.status} ${await res.text()}`);
const data = await res.json();

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.