Miravia Scraper avatar

Miravia Scraper

Pricing

from $0.01 / 1,000 dataset results

Go to Apify Store
Miravia Scraper

Miravia Scraper

Scrape Miravia search results, categories, products, reviews, sellers, and marketplace discovery feeds without maintaining anti-bot headers, signatures, cookies, browser sessions, or mobile API behavior.

Pricing

from $0.01 / 1,000 dataset results

Rating

0.0

(0)

Developer

Charted Sea

Charted Sea

Maintained by Community

Actor stats

0

Bookmarked

2

Total users

1

Monthly active users

11 hours ago

Last modified

Categories

Share

Scrape Miravia search results, categories, products, reviews, and sellers without maintaining anti-bot headers, signatures, cookies, or browser sessions.

The Actor accepts Miravia page URLs and backend API URLs for Spain. Each request is processed independently and produces one row in the default dataset.

Quick start

{
"requests": [
{
"url": "https://www.miravia.es/catalog/?q=tshirt"
}
]
}

A run accepts 1 to 100 requests. The Actor waits for every request to reach a terminal state before publishing results and charging finalized events.

Input

Shared options apply to every request. A value inside an individual request overrides the shared value for that request.

  • requests - Required array containing 1 to 100 Miravia requests.
  • emulateMobileDevice - Emulate mobile web traffic. Default: false.
  • language - Optional request language.

Per-request fields:

  • url - Required Miravia page or backend API URL.
  • method - GET. Default: GET.
  • Any shared option above - Overrides that option for this request.

cleanResponseBody is not supported. Unknown request options are passed to the backend for forward compatibility.

Product search and Seller products options

These options affect only Product search and Seller products requests, whether supplied at the input or request level:

  • productListing_crawlNextPages - Crawl subsequent listing pages.
  • productListing_crawlNextPages_maxPages - Maximum listing pages.
  • productListing_crawlNextPages_maxUniqueProducts - Maximum unique products.
  • productListing_crawlNextPages_stopWhenNewPageOnlyContainsDuplicates - Stop on a page containing only products already collected. Default: true.
  • productListing_crawlNextPages_stopWhenNoMorePagesIsTrue - Stop when Miravia reports no more pages. Default: true.

Supported Miravia APIs

Product search by keyword, category, or seller

https://www.miravia.es/catalog/?q=${keyword}
https://www.miravia.es/c/${categorySlug}-${categoryId}/
https://www.miravia.es/${sellerKey}/?q=All-Products&from=wangpu&langFlag=en-ES&pageTypeId=2&search_scenario=store&src=store_allproducts&sellerKey=${sellerKey}

Avoid adding page directly. Miravia requires sequential navigation from the first page. Use productListing_crawlNextPages for multi-page crawling.

{
"requests": [
{ "url": "https://www.miravia.es/catalog/?q=tshirt" },
{ "url": "https://www.miravia.es/c/camisetas-para-mujer-100195/" },
{ "url": "https://www.miravia.es/inside/?q=All-Products&from=wangpu&langFlag=en-ES&pageTypeId=2&search_scenario=store&src=store_allproducts&sellerKey=inside" }
]
}

Examples:

Product details

https://www.miravia.es/p/i${productId}.html
https://www.miravia.es/p/${productSlug}-i${productId}.html
{
"requests": [
{ "url": "https://www.miravia.es/p/i1374784873099279.html" }
]
}

Product detail example

Product reviews

https://www.miravia.es/pdp/review/getReviewList?itemId=${productId}

Only the initial review page is supported.

Product reviews example

Category navigation

https://acs-m.miravia.es/h5/mtop.lazada.guided.shopping.categories.categorieslpcommon/1.0/

This endpoint extracts Miravia's category navigation, not a complete category tree.

Category navigation example

Seller details

https://www.miravia.es/shop/${sellerKey}/

Seller detail example

Seller promoted products

https://www.miravia.es/shop/site/api/shop/campaignTppProducts/query?shopId=${shopId}&sellerId=${sellerId}&itemId=${productId}

Use offset=20 for the second 20-item page.

Seller promoted products example

Keyword listing

https://www.miravia.es/sitemap-d7df5b64df1181ef1d62d646a13aaa86.xml?limit=${limit}&offset=${offset}

Keyword listing example

Unsupported APIs

Miravia does not support:

  • Product Reviews V2 at https://acs-m.miravia.es/h5/mtop.lazada.review.item.getpcreviewlist/1.0/.
  • Seller listing at https://www.miravia.es/sitemap-sellers.xml.

Unsupported requests are rejected before execution and are not billed.

Output

The default dataset contains one row per input request:

{
"marketplaceRunUuid": "...",
"taskUuid": "...",
"url": "https://www.miravia.es/catalog/?q=tshirt",
"status": "SUCCESS",
"responseBody": {}
}

Output fields:

  • marketplaceRunUuid - Marketplace run ID.
  • taskUuid - Task ID.
  • url - Original requested URL.
  • status - Terminal request status.
  • responseBody - Native Miravia response for a successful request.
  • error - Error description for an unsuccessful request.

Rows remain in the same logical request order. One failed request does not hide successful rows from the same batch.

  • AliExpress Scraper - Scrape AliExpress searches, products, reviews, sellers, and categories.

Pricing and charging

Pay as you go with no subscription or monthly minimum:

  • Successful Miravia request: $0.00272 per request, or $2.72 per 1,000 successful requests.
  • Proxy usage: $0.00013 per started block of 100 proxy units.
  • Actor start: $0.00005 per GB of Actor memory, with a minimum of one event.
  • Dataset result: $0.00001 per result written to the default dataset.

This is a PAY_PER_EVENT Actor. It charges one csea-scrape-miravia event per successful Miravia request and finalized csea-proxy-unit events for proxy usage. Failed or cancelled requests are not charged as successful Miravia requests. Use Apify's maximum total charge setting to bound an execution's cost.

Graceful aborts and retries

A graceful Apify abort cancels known scraping tasks and waits for backend finalization. Interrupted Actor executions persist their marketplace-run, charging, and output state so they can resume without intentionally duplicating charges or dataset rows.

Operational guidance

  • Monitor success rates during major Miravia campaigns.
  • Expect stricter anti-bot behavior during high-traffic sales.
  • Prefer bounded listing crawls over unbounded multi-page requests.