canonical: https://jentic.com/apis/open.lazada.com/lazada

# Open Lazada Lazada Open Platform API

Jentic publishes the only available OpenAPI specification for Lazada Open Platform API, keeping it validated and agent-ready. Lazada is one of Southeast Asia's largest online marketplaces, and its Open Platform exposes seller-facing operations across products, orders, reviews, seller performance, and category metadata. The endpoints in this spec cover the read-side of the platform - list products, fetch a product, read seller and product reviews, pull order and order-item data, and walk the category tree - so it is well suited to agents that monitor, analyse, or sync a Lazada storefront rather than directly mutating listings.

## For AI agents

Read Lazada storefront data - product listings, orders, reviews, and seller performance - through the Open Platform. Useful for agents that monitor or sync a Lazada seller account.

## Scope

Does not create listings, update prices or stock, initiate shipments, or process refunds - use for read-side Lazada product, order, review, seller, and category lookups only.

## Capabilities

- List products in a Lazada seller's catalogue with paging support
- Fetch the full record for a single product including attributes and SKU detail
- Pull product reviews and seller reviews for reputation tracking
- Read seller performance metrics that drive Lazada's seller scoring
- List orders and drill into individual order items for fulfilment workflows
- Walk the Lazada category tree and read the attribute schema for a category

## Use cases

### Lazada Order Sync

Pull new and updated Lazada orders into a fulfilment system on a schedule. GET `/orders/get` returns paged orders filtered by status and date, GET `/order/get` returns the full record for a specific order, and GET `/order/items/get` returns the line items, which together cover the read-path a fulfilment agent needs.

Example prompt: Every 10 minutes, call GET `/orders/get` with status='unpacked' and pull the matching order ids; for each, call GET `/order/items/get` and push the items to the fulfilment queue.

### Product Rating Monitoring

Track ratings and review trends for products in a Lazada storefront so a brand-protection agent can flag a sudden drop in star rating or a spike in negative reviews. GET `/review/product/get` returns reviews and GET `/products/get` returns the live rating, which the agent can diff against yesterday's snapshot.

Example prompt: Pull the current rating for each product via GET `/products/get` and any new reviews via GET `/review/product/get`; alert when the average rating drops more than 0.3 points week-on-week.

### Seller Performance Reporting

Pull Lazada's seller-performance metrics to render a dashboard for a marketplace operations team. GET `/seller/performance/get` and GET `/seller/metrics/get` return the structured metric snapshots Lazada uses internally for seller scoring, suitable for daily reporting.

Example prompt: Each morning, call GET `/seller/performance/get` and post the on-time-shipment rate and cancellation rate to the operations channel.

### Category Schema Discovery

Resolve the correct Lazada category for a new listing and pull the attribute schema before posting. GET `/category/tree/get` returns the tree and GET `/category/attributes/get` returns the per-category attributes, which a listing-creation agent uses to build a valid product payload elsewhere.

Example prompt: Call GET `/category/tree/get` and find the leaf category for 'Wireless Earbuds', then call GET `/category/attributes/get` for that category id and return the required attributes.

### AI Agent Marketplace Sync

Let a Jentic-orchestrated agent keep an external order-management system in sync with Lazada without holding the access token. Jentic injects the access_token query parameter at execution time, the agent runs the read flow, and the resulting payloads are pushed downstream.

Example prompt: Search Jentic for 'list Lazada orders', load the GET `/orders/get` schema, and execute it for orders updated in the last 24 hours, returning the order ids for downstream sync.

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/products/get` | List products in the seller catalogue |
| GET | `/product/item/get` | Get a single product's full detail |
| GET | `/orders/get` | List orders for the seller |
| GET | `/order/items/get` | Get the line items for a specific order |
| GET | `/review/product/get` | Get reviews for a product |
| GET | `/seller/performance/get` | Get seller performance metrics |
| GET | `/category/tree/get` | Walk the Lazada category tree |
| GET | `/category/attributes/get` | Get the attribute schema for a category |

## Key resources

- **Products** — List products and fetch single product detail.
- **Reviews** — Read product reviews and seller reviews.
- **Seller** — Seller information, performance, and metrics.
- **Orders** — List orders and drill into individual order items.
- **Categories** — Walk the category tree and read per-category attribute schemas.

## Why Jentic

- **Setup:** Wiring the Lazada Open Platform API by hand means passing your access_token query parameter, choosing the right regional host such as the Singapore or main endpoint, and handling its signing conventions yourself. Through Jentic you install once, import the Lazada Open Platform API from the API Directory, store the access token once, and your agent calls it.
- **Permission scoping:** The Lazada read-side operations here take product and order identifiers as query parameters rather than a resource id in the URL path, so limit the agent to the operations it needs, such as listing products, reading orders, or fetching reviews. You credit the agent only with the operations you allow.
- **Credential handling:** Your Lazada access token is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list seller orders' or 'get a product's detail', and Jentic returns the matching Lazada operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopee Open API** — Direct competitor in Southeast Asian e-commerce with a similar seller-facing surface.
- **Tokopedia API** — Indonesian marketplace with seller, product, and order endpoints.
- **Shopify API** — Storefront platform commonly used as the source of truth for products synced to marketplaces.

## FAQ

### Why is there no official OpenAPI spec for Lazada Open Platform API?

Lazada publishes its developer documentation on open.lazada.com but does not ship a single machine-readable OpenAPI document. Jentic generates and maintains this spec so AI agents and developers can call Lazada Open Platform API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer.

### What authentication does the Lazada Open Platform API use?

Lazada uses an access_token query parameter obtained through its app authorisation flow. Through Jentic the token is held in the vault and appended at execution time so the agent never sees the raw token in its prompts or URLs.

### Can I create or update products with this Lazada API spec?

The 12 endpoints in this spec cover the read-path - list products, get product detail, list orders, read reviews and seller metrics, walk categories. Listing creation and price or stock updates use separate Lazada endpoints not in this spec, so an agent that needs to mutate a listing should add those endpoints in a follow-up.

### What are the rate limits for the Lazada Open Platform API?

Lazada applies per-app and per-shop rate limits that are not declared in this spec; the platform documentation describes app-level QPS quotas in the seven-figure-monthly range with per-second throttling. Plan for 429 handling and back off on rate-limit responses.

### How do I list Lazada orders through Jentic?

Run pip install jentic and search for 'list Lazada orders'. Jentic returns the GET `/orders/get` operation; load the schema and execute it with the desired status and date filter to receive the order list, then chain into GET `/order/items/get` for each order.

### Does this spec cover all Lazada regional sites (SG, MY, ID, etc.)?

The base URL is https://api.lazada.com/rest with regional alternates such as https://api.lazada.sg/rest. The endpoint paths are identical across regions; the difference is which base URL the access token was issued against, so an agent should select the regional base URL that matches the seller's country.

### Can I limit what my agent is allowed to do with the Lazada Open Platform API?

Yes. Because Jentic One runs self-hosted, your own rules decide which Lazada operations and credentials the agent may use, and these read-side operations take product and order identifiers as query parameters rather than in the URL path. You can allow only the calls the agent needs, such as listing products with GET `/products/get`, reading orders with GET `/orders/get`, or fetching reviews with GET `/review/product/get`, and withhold the rest. The agent is credited only with the operations you grant, so it cannot reach beyond that scope.