dataweboteMAG scraper API for AI agents and code
datawebot returns eMAG search results as structured JSON, with the same fields for every shop: title, price, original price, availability, rating, image and link. It runs from your AI agent over MCP or from code over REST on emag.ro in Romania, at 5 credits per search page, and failed requests are free.
Fields you get
Every eMAG product comes back in these fields; a field is null when the page doesn't show it. Each endpoint below also lists its raw record schema.
| Field | Type | Description |
|---|---|---|
product_id | string or null | Opaque id. Pass it to get_product (or capability "product") to read the product again. |
title | string | Product title as the shop shows it. |
url | string or null | The product page on the shop. |
shop | string or null | The shop’s hostname, without www. |
price | object or null | amount (number), currency (ISO 4217, or null when the shop doesn’t say) and text (the shop’s own wording when it is the same amount, else null). |
original_price | object or null | The price before a discount, in the same shape as price. |
rating | number or null | Average rating, on the shop’s own scale. |
review_count | integer or null | Number of reviews or ratings. |
image_url | string or null | Main product image. |
availability | string or null | in_stock, out_of_stock, or the shop’s own stock wording. |
sponsored | boolean or null | true for an ad the shop marks as sponsored; null when the page doesn’t say. |
How to run it
From your agent, after connecting it once with the setup prompt (agent setup), ask in plain words:
Use datawebot to extract https://www.emag.ro/search?query=laptop+lenovo and give me each product's title, price and link as JSON.From code, send one request with your API key. The answer has the same shape for every shop; if it says "status": "working", read it again with GET /v1/requests/{id}.
curl https://api.datawebot.com/v1/requests \
-H "Authorization: Bearer $DATAWEBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"capability":"endpoint","endpoint":"emag.search_items","url":"https://www.emag.ro/search?query=laptop+lenovo","format":"structured"}'Search
eMAG Romania (www.emag.ro) keyword search: the first 1-5 main-grid cards of the first results page in grid order, with PNK, numeric product and offer IDs, title, display seller, the selected listing offer price in RON, stock text, badges and prior-price text. Search only: no product pages, pagination, filters or sorting.
- ID
emag.search_items- Version
1- Price
- 5 credits / page
- State
- Available
- Typical time
- About 30 s (estimate)
What it does
Reads one search results page (or up to the page limit) and returns one record per product card, in page order. Works on www.emag.ro; other hosts are rejected before anything runs.
Input
One page URL per request, shaped like https://www.emag.ro/search?query=laptop+lenovo, plus these bounded parameters.
| Parameter | Type | Allowed | Default | Set in /v1/requests |
|---|---|---|---|---|
max_products | integer | 1–5 | 5 | POST /v1/jobs only |
Price
5 credits / page. Failed requests are free; a page that loaded but had nothing on it still costs credits. Set max_credits to refuse anything dearer before it runs.
Output
The default, "format": "structured". Every shop answers in the same fields, mapped from the page to the product_summary@1 schema. Fields are null when the page doesn't show them, and a record that can't be mapped is read best-effort from its raw fields. Products are in products, up to 50 a page; follow next_cursor with GET /v1/requests/{id} (MCP: get_results).
| Field | Type | Description |
|---|---|---|
product_id | string or null | Opaque id. Pass it to get_product (or capability "product") to read the product again. |
title | string | Product title as the shop shows it. |
url | string or null | The product page on the shop. |
shop | string or null | The shop’s hostname, without www. |
price | object or null | amount (number), currency (ISO 4217, or null when the shop doesn’t say) and text (the shop’s own wording when it is the same amount, else null). |
original_price | object or null | The price before a discount, in the same shape as price. |
rating | number or null | Average rating, on the shop’s own scale. |
review_count | integer or null | Number of reviews or ratings. |
image_url | string or null | Main product image. |
availability | string or null | in_stock, out_of_stock, or the shop’s own stock wording. |
sponsored | boolean or null | true for an ad the shop marks as sponsored; null when the page doesn’t say. |
{
"request_id": "string",
"status": "done",
"products": [
{
"product_id": "string or null",
"title": "string",
"url": "string or null",
"shop": "string or null",
"price": {
"amount": "number",
"currency": "string or null",
"text": "string or null"
},
"original_price": {
"amount": "number",
"currency": "string or null",
"text": "string or null"
},
"rating": "number or null",
"review_count": "integer or null",
"image_url": "string or null",
"availability": "string or null",
"sponsored": "boolean or null"
}
],
"next_cursor": "string or null",
"meta": {
"as_of": "date-time",
"country": "string",
"credits_used": "integer",
"credits_left": "integer"
}
}Over the Jobs API, GET /v1/jobs/{id}/results?format=structured returns the full product_summary@1 records.
With "format": "raw", the answer keeps the structured fields and adds raw: this endpoint's own records, unchanged, one per item, in the schema below. It is the data the endpoint extracted from the page, not the page's HTML. Same price as structured.
| Field | Type | Description |
|---|---|---|
rank | integer required | 1-based main-grid position on page 1 |
url | string (uri) required | Pattern ^https://www\.emag\.ro/[^/]+/pd/[A-Z0-9]+/$ |
pnk | string required | eMAG product code from the URL |
product_id | string required | Literal numeric product ID |
offer_id | string required | Literal selected listing offer ID |
title | string required | — |
seller_name | string or null required | Listing display seller name, not a legal entity |
seller_id | null required | — |
price | string required | Displayed selected listing offer price, cross-checked with card metadata |
currency | "RON" required | — |
price_scope | string required | — |
availability_text | string or null required | Source text; not a stock promise |
shipping | null required | — |
vat | null required | — |
selected_variant | null required | — |
conditional_price | null required | — |
badges | array required | Observations, not discounts |
previous_price_text | string or null required | Observation, not an unconditional saving |
sponsored | null required | — |
{
"rank": "integer",
"url": "string (uri)",
"pnk": "string",
"product_id": "string",
"offer_id": "string",
"title": "string",
"seller_name": "string or null",
"seller_id": null,
"price": "string",
"currency": "RON",
"price_scope": "string",
"availability_text": "string or null",
"shipping": null,
"vat": null,
"selected_variant": null,
"conditional_price": null,
"badges": "array",
"previous_price_text": "string or null",
"sponsored": null
}Raw needs this endpoint: a search with format: "raw" doesn't fall back to shopping search, and answers raw_unavailable where no endpoint can run. Over the Jobs API, results are raw by default; format=both gives each raw record with its structured form.
Request
Run exactly this endpoint with capability: "endpoint"; there is no fallback, and a failed run is free. Set format to "raw" for the raw records too. For a keyword instead of a URL, search_products with this shop as site builds the search URL, tries the shop's endpoint first and then shopping search.
curl https://api.datawebot.com/v1/requests \
-H "Authorization: Bearer $DATAWEBOT_API_KEY" \
-H "Content-Type: application/json" \
-d '{"capability":"endpoint","endpoint":"emag.search_items","url":"https://www.emag.ro/search?query=laptop+lenovo","format":"structured"}'submit_job {
"endpoint": "emag.search_items",
"url": "https://www.emag.ro/search?query=laptop+lenovo",
"format": "structured"
}If the answer says "status": "working", read it again with GET /v1/requests/{id} (MCP: get_results) after check_after_seconds.
Limits
- One page URL per request, on emag.ro only; other hosts are rejected before anything runs.
- Prices and stock are read when the request runs (
meta.as_of); datawebot keeps no price history, so schedule and store repeat reads yourself. - Fields the page doesn't show come back null; nothing is filled in or guessed.
- Up to 30 requests a minute per account.
Questions about the eMAG scraper API
Does eMAG have an official API?
datawebot does not use one. It reads eMAG's pages and returns them as structured JSON, so you need no eMAG developer account or partner key. Whether eMAG offers its own API, and on what terms, is for eMAG to say.
Can I scrape eMAG with Python?
Yes. Send the POST /v1/requests call shown on this page from Python with any HTTP client, such as requests or httpx: the same JSON body, with your API key in the Authorization header. The products come back in the answer's products field (product for a product page).
Is it legal to scrape eMAG?
It depends on where you are, eMAG's terms and what you do with the data. You stay responsible for how you use what datawebot returns. This is not legal advice; read our guide to robots.txt and legal considerations, and ask a lawyer about your case.
What does a eMAG scraper API call cost?
5 credits per search page. Failed requests are free; a page that loaded but had nothing on it still costs credits. Every account starts with 200 free credits, and credit packs start at 10,000 credits for $10, with no subscription.
Start with 200 free credits
Connect your agent with one setup prompt, or create an API key, and run eMAG requests right away. No card and no subscription.
Connect your agent See pricing