Skip to content

Web data for e-commerce teams

Price monitoring, assortment tracking and marketplace research all start with the same three questions: what does this product cost, where, and is it in stock. Microlink answers them with extraction rules on product pages, the Search API on Google Shopping and a country-pinned proxy for localized prices, all behind one API key.

Recipes

Pick the job you are automating

Product prices and stock

Read prices as numbers and stock as text from any product page, with fallback rules that survive template changes.

Scrape prices by country

One extraction request per market, pinned to its country, merged into a table of comparable prices and currencies.

Price comparison from Google Shopping

Get every merchant Google Shopping lists for a product, with a numeric price, the merchant name and the rating, per country.

Tables and lists to JSON arrays

Turn table rows, product grids and search results into an array of objects, one nested rule per column.

Region-specific metadata

Fetch titles, descriptions and prices as a visitor from a given country and language sees them.

Screenshot a site from another country

Pin the request to a country with a two-letter code and capture the prices and copy a local visitor sees.
How it fits together

From a product URL to a price history

Most e-commerce pipelines combine discovery, extraction and localization. Each step is one API call, so you can start with any of them.

01 · Discover
Find who sells the product.
A Google Shopping query returns merchants, prices already parsed as numbers and ratings, so you know which stores to watch before writing a single selector.

See Google Shopping price comparison for the query and the result fields.

02 · Extract
Read price and stock from the product page.
CSS selector rules return exactly the fields you name, typed as numbers or strings, with fallbacks for stores that change their markup.

The product prices recipe covers typed prices, fallback selectors and JavaScript-rendered stores.

03 · Localize
See the price a shopper in each country sees.
Pin the proxy to a country and run the same rules once per market. On Pro plans the proxy also handles the antibot walls that big retailers put in front of product pages.

When not to: if the store publishes a feed or an affiliate API, read that first. Scraping is for the stores that do not.

Scope

What you still build

Microlink returns the page as data, one request at a time. It does not schedule requests, keep a price history or send alerts, so the loop that runs every hour, the table that stores each reading and the rule that flags a price drop live in your code.

That split keeps you in control of cadence and cost: cache hits never count toward your quota, and ttl decides how fresh each reading must be.

FAQ

Can I monitor competitor prices with an API instead of a scraper?

Yes. Extraction rules turn any product page into JSON with the fields you name, and the Google Shopping search type lists merchants and prices for a query. You run them on your own schedule and store the results.

How do I get the price shown in another country?

Set proxy.location to a two-letter country code on a Pro plan and run the same extraction rules once per country. See prices by country.

What happens when a store blocks scrapers?

On Pro plans the proxy is automatic: when a request hits an antibot wall, Microlink escalates through proxy tiers up to residential and remembers what worked for that domain. On the free tier the API answers with EPROXYNEEDED instead.
No. Microlink returns the current data on each request. Scheduling, storing the history and deciding what counts as a change are up to your application.

Ready to track prices from any store?

Start on the free tier with extraction rules, add a Pro key when you need proxies, countries or longer caching.