For 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.
Install Jentic One Beta
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Lazada Open Platform API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | shStep 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
What an agent can do with Lazada Open Platform API.
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
GET STARTED
Use for: List the products in my Lazada seller account, Get full details for a specific Lazada product, Pull recent reviews for a Lazada product, Read my Lazada seller performance metrics
Not supported: 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.
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.
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
Patterns agents use Lazada Open Platform API for, with concrete tasks.
★ 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.
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.
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.
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.
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.
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.
12 endpoints — jentic publishes the only available openapi specification for lazada open platform api, keeping it validated and agent-ready.
METHOD
PATH
DESCRIPTION
/products/get
List products in the seller catalogue
/product/item/get
Get a single product's full detail
/orders/get
List orders for the seller
/order/items/get
Get the line items for a specific order
/review/product/get
Get reviews for a product
/seller/performance/get
Get seller performance metrics
/category/tree/get
Walk the Lazada category tree
/category/attributes/get
Get the attribute schema for a category
/products/get
List products in the seller catalogue
/product/item/get
Get a single product's full detail
/orders/get
List orders for the seller
/order/items/get
Get the line items for a specific order
/review/product/get
Get reviews for a product
Three things that make agents converge on Jentic-routed access.
Credential isolation
The Lazada access_token is stored encrypted in the Jentic vault (MAXsystem). Jentic appends it as the access_token query parameter at execution time so the raw token never enters the agent's context or appears in logs.
Intent-based discovery
Agents search Jentic with intents such as 'list Lazada orders' or 'pull Lazada product reviews' and receive the matching open.lazada.com endpoint with its full input schema, including the regional base URL options.
Time to first call
Direct Lazada integration: 3-5 days for the OAuth-style app-authorisation flow, signature handling, and per-region base URLs. Through Jentic: under 1 hour — search, load schema, execute.
Alternatives and complements available in the Jentic catalogue.
Specific to using Lazada Open Platform API through Jentic.
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 at https://app.jentic.com/sign-up.
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.
/seller/performance/get
Get seller performance metrics
/category/tree/get
Walk the Lazada category tree
/category/attributes/get
Get the attribute schema for a category