Miravia Spain Scraper at a glance
Miravia Spain Scraper is a ready-to-run Apify actor from abotapi for collecting web data. Its output documents 52 fields, including recordid, rowtype, productid, skuid and product, which you can export as JSON, CSV or Excel or read through the Apify API. It costs $2.00 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify.
- Runs on
- Apify cloud: console, API, schedules and integrations
- Data type
- Web data
- Region
- Europe
- Pricing
- $2.00 per 1,000 results (Free plan), from $1.50 on paid plans
- Output
- 52 documented fields · JSON, CSV, Excel
- Inputs
- 22 options
What Miravia Spain Scraper: Products, Prices, Stores can do
- Two ways in. Search by keyword, or paste product, search, category, keyword and shop links (a shop link resolves to its seller and walks that assortment). No need to build URLs by hand.
- The price pair is on every row. Selling price, original price, discount percent, brand, seller, rating and promotion flags come from the search page itself, with no second request.
- Store depth on demand. Switch product details and reviews on or off per run, and pay only for what you use. Reviews bill per started block of 10.
- Seller stores as first-class scopes. Paste a seller-store link to walk that seller's assortment (resolved through the storefront search for the shop's own name), filter any walk to a single seller id, and read each store's rating, followers and on-time shipping.
- Built for schedules. Incremental mode returns only new and changed products on recurring runs, image galleries never mark a row changed on their own, and a refused run fails loudly instead of returning an empty dataset.
Choose what to collect
These inputs let you configure Miravia Spain Scraper: Products, Prices, Stores. Open the actor on Apify to enter your values and review the current options.
| Input | What it controls |
|---|---|
modestring · required | How to start the scrape. 'search' runs storefront searches. 'url' processes the Miravia URLs you paste: a product URL returns that single product in full, and a search, category, keyword or shop URL is walked like a search, its own scope deciding what is read. A shop URL is resolved to its seller identity then walked through the storefront search for the shop's own name, keeping only that seller's rows. The legacy 'shop' mode value still parses as 'url'. The filters below apply to every walk in both modes; a pasted product URL is the one exception and returns that single product in full. |
searchTermsarray | One or more things to search Miravia Spain for, for example 'lego', 'air fryer', 'zapatillas running'. Each term is scraped independently. Search mode only: in URL mode the scope is read out of the pasted URL instead. Leave this empty and the run browses the whole storefront with only the filters applied. |
categoryIdstring | Narrow every search walk to one Miravia category id, for example '19131' (Building Sets). The id is read from the storefront's own category facet on any search page. Search mode only: in URL mode the pasted link decides its own scope. Leave empty for all categories. |
sellerIdstring | Keep only rows sold by one seller id, for example '4000015456014'. The storefront has no parameter for this, so it is applied to the rows this run reads. Combine with a pasted shop URL or with a search to audit one seller's assortment. Leave empty for all sellers. |
urlsarray | Paste product URLs (https://www.miravia.es/p/i1374428537687072.html, the SEO https://www.miravia.es/p/lego-set-i1374428537687072.html and the variant https://www.miravia.es/p/lego-set-i1374428537687072-s2091201667636256.html forms all work), keyword URLs (https://www.miravia.es/kw/lego.html), search URLs (https://www.miravia.es/c/all/?q=lego), category URLs (https://www.miravia.es/c/juegos-de-construccion-19131/?q=lego) and seller-store URLs (https://www.miravia.es/shop/lego-official/, resolved to the seller and walked like a search keeping only that seller's rows). A pasted URL decides its own scope. Add &page=3 to a pasted search or category URL to start the walk further in; a product URL ignores paging and returns that one product in full. The filters below narrow what the walks read: the ordering filter is sent to the storefront with every page, and the price bounds, Discounted rows only and Only this seller are applied to the rows this run reads. |
sortBystring | The storefront's own server-side ordering, sent with every page of every walk. This orders the walk itself (and therefore which rows a capped run keeps), not just the output. Applies in ALL modes. |
minPricenumber | Only keep rows whose selling price is at least this many euros. The storefront has no parameter for this, so it is applied to the rows this run reads. Applies in ALL modes. |
Show 15 more inputs
| Input | What it controls |
|---|---|
maxPricenumber | Only keep rows whose selling price is at most this many euros. The storefront has no parameter for this, so it is applied to the rows this run reads. Applies in ALL modes. |
onSaleOnlyboolean | Only keep rows whose selling price is below the original price, that is rows with a discount. The storefront has no parameter for this, so it is applied to the rows this run reads. Applies in ALL modes. |
fetchDetailsboolean | Fetch each item's product page for the description, the attribute table, the SKU variants with per-variant prices and stock, the full image gallery, the seller store object (rating, followers, on-time shipping), delivery options, warranties and the promotion. Slower, and charged per record under the detail-enrichment surcharge. Leave off for a fast crawl: identity, prices, discount, brand and seller are included either way. |
fetchReviewsboolean | Fetch each item's customer reviews: the rating summary (score, count and the star breakdown) and the most recent reviews up to Max reviews per product. The storefront serves the first reviews page on the product page itself, so this is a cap, not a pagination promise: rows beyond it are not fetched. Charged under the same detail-enrichment surcharge (never twice, even with Fetch product details also on): one unit per record plus one unit per started block of 10 reviews. Leave off by default. |
maxItemsinteger | The single cap on this run: stop after collecting this many records across all searches, stores and URLs. Set 0 for unlimited. |
maxPagesinteger | Safety bound on how many result pages to walk per search term, store or URL. Leave empty (0) for no page limit: the run then stops at Max items, not here. Does not impose a separate cap below Max items. |
resumeFromRunIdstring | Paste a previous run ID or dataset ID to continue a large crawl without returning or charging for records already collected there. Use this after an interrupted or capped run. For recurring monitoring of the same search, use Incremental mode below instead. |
incrementalModeboolean | Turn this on for daily or weekly recurring monitoring of the same search or pasted URLs, for example a price watch. The first run returns everything matching as NEW. Later runs normally return only NEW, UPDATED and REAPPEARED records. Price moves and stock changes ARE reported as UPDATED: on a storefront they are the signal, not noise. Image galleries never mark a row UPDATED on their own. Turn on Emit unchanged or Emit expired only when you also want those rows returned (and billed). State is kept separately per search, URL and filter setup; use State key to name or deliberately share a monitoring campaign. To continue one specific interrupted run instead, use Resume from a previous run above. |
stateKeystring | Optional. Name this monitoring campaign to keep its state stable, or to deliberately share state across differently configured runs. Leave empty to let the actor derive a key automatically from the searches, URLs and filters, so two different scopes never mix state. |
emitUnchangedboolean | Off by default. Turn on to also return records that have not changed since the last run, marked UNCHANGED. This returns, and bills, extra rows you already have, so leave it off unless you specifically want a full snapshot every run. |
emitExpiredboolean | Off by default. Turn on to also return records that were present in a previous run but are no longer found, marked EXPIRED. Only produced once a run has fully scanned the tracked scope: not when Max items capped it, not when Resume was used, and not when the run was refused. This returns, and bills, extra synthetic rows, so leave it off unless you need expiry tracking. |
ignoreFieldsForChangesarray | Extra top-level record fields that must never mark a row UPDATED in incremental mode, on top of the built-in image URL guard. Use this when a field moves between runs without the product changing. Leave empty for the default behaviour. |
mcpConnectorsarray | Optionally send results into the apps you already use, via Model Context Protocol (MCP) connectors. Authorize one under Apify, Settings, API and Integrations, then select it here. Notion gets a page per record; other connectors get a best-effort write or digest. Each connector receives a condensed summary per record, not the full record; the complete record always stays in the dataset. Leave empty to skip; this never changes the dataset output. Supported: Notion (https://mcp.notion.com/mcp), Linear (https://mcp.linear.app/sse), Airtable (https://mcp.airtable.com/mcp), Apify (https://mcp.apify.com). |
notionParentPageUrlstring | URL or id of the Notion page under which record pages are created. Required to enable the Notion export; ignored by other connectors. |
maxNotifyListingsinteger | Cap on records written to each connector per run. Does not affect the dataset. |
Fields in the output
The documented dataset includes the fields below. Availability can depend on the source page and selected mode.
recordIdrecordIdrowTyperowTypeproductIdproductIdskuIdskuIdtitleProduct (text)brandBrand (text)pricePrice (number)priceTextPrice (as shown) (text)originalPriceOriginal price (number)originalPriceTextoriginalPriceTextonSaleOn sale (text)discountPercentDiscount % (number)Show 40 more fields
currencyCurrency (text)imageUrlImage (image)sellerIdsellerIdsellerNameSeller (text)officialStoreOfficial store (text)ratingRating (number)reviewCountReviews (number)soldCountSold (number)inStockIn stock (text)isSponsoredisSponsoredpromotionTagsPromotions (array)descriptionDescription (text)attributesattributesskusskusimageUrlsimageUrlsstorestorereviewTotalreviewTotalreviewsreviewsurlURL (link)changeTypeChange type (incremental mode) (text)changedFieldsChanged fields (incremental mode) (array)firstSeenAtFirst seen (incremental mode) (date)lastSeenAtLast seen (incremental mode) (date)highlightshighlightsskuOptionsskuOptionsphotoCountPhotos (number)sellersellerdeliveryOptionsDelivery (array)warrantieswarrantiescampaigncampaignratingBreakdownRating breakdown (text)aiSummaryAI summary (text)detailCarriedForwardRepaired from previous run (text)reviewIdreviewIdreviewRatingRating (number)reviewTextReviewreviewBuyerBuyerreviewDateDate (date)reviewMediareviewMediareviewLikesLikes (number)Example output
An example from this actor’s documentation. Values are illustrative; this is not a fresh live result.
{
"recordId": "miravia:1000000000000001",
"rowType": "product",
"productId": "1000000000000001",
"skuId": "2000000000000001",
"title": "Sample Building Set 500 Pieces",
"brand": "Sample Brand",
"price": 19.99,
"priceText": "19,99EUR",
"originalPrice": 29.99,
"onSale": true,
"discountPercent": 33.3,
"currency": "EUR",
"sellerId": "4000000000001",
"sellerName": "Sample Store",
"rating": 4.8,
"reviewCount": 120,
"soldCount": 350,
"url": "https://www.miravia.es/p/i1000000000000001.html",
"description": "A 500-piece building set with... (with Fetch product details)",
"attributes": [
{
"name": "Pieces",
"value": "500"
}
],
"skus": [
{
"skuId": "2000000000000001",
"price": 19.99,
"sold": 350
}
],
"imageUrls": [
"https://img.mrvcdn.com/...jpg"
],
"photoCount": 8,
"store": {
"storeName": "Sample Store",
"rating": 4.9,
"followers": "10.2K"
},
"deliveryOptions": [
{
"title": "Standard",
"feeText": "Free shipping"
}
],
"ratingBreakdown": {
"score": 4.8,
"totalReviews": 120
},
"reviewTotal": 120,
"reviews": [
{
"reviewText": "Great set...",
"reviewRating": 5,
"reviewBuyer": "Sample Buyer"
}
]
}Ways to use this data
- Price monitoring and repricing: track selling and original prices, discounts and stock signals across Miravia Spain on a schedule.
- Assortment and seller research: walk a seller store to audit its catalog, ratings and promotions, or compare sellers on the same keywords.
- Deal discovery: filter to discounted rows only, sort by price, and bound any run with minimum and maximum prices.
- Catalog building and data science: collect titles, attributes, variants, galleries and reviews for search, recommendations or analytics.
- Review and reputation tracking: follow rating distributions and recent customer reviews per product over time.
Before you run
Start with a small input and check the resulting records against your expected fields. Source content and actor options can change; the current Apify listing is the reference for availability and pricing.
Questions about this actor
What data does Miravia Spain Scraper return?
Miravia Spain Scraper returns 52 documented fields, including recordid, rowtype, productid, skuid, product, brand, price and price (as shown). Availability of each field depends on the source page and the selected mode.
How much does Miravia Spain Scraper cost?
It costs $2.00 per 1,000 results on the Apify Free plan and from $1.50 on paid plans, with smaller per-run or optional feature charges listed on Apify. The Apify listing shows the current rate for every plan.
Can I get only new or changed products on a schedule?
Yes. Schedule the actor from the Schedules tab and turn on Incremental mode. Each run then returns only new and updated records, and unchanged ones are not billed. Image galleries never mark a row changed on their own.
Why did a run return fewer products than the storefront shows?
Search mode stops at Max items, most popular first. Set it higher, or to 0, to collect the whole scope. Price bounds, the sale flag and the seller scope also narrow what is kept: widen them to get more rows.
Why did my run fail instead of returning an empty dataset?
If the storefront refuses every request, the run stops with a clear message so "no products today" is never confused with "nothing could be read". Run it again in a few minutes. If only some searches or URLs could be read, you still get what was found.
Can I use it with AI agents or MCP?
Yes. Call it from any Apify integration or MCP client, and use the connector field to push results into Notion, Linear or Airtable.
