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.
Pick the job you are automating
Product prices and stock
Scrape prices by country
Price comparison from Google Shopping
Tables and lists to JSON arrays
Region-specific metadata
Screenshot a site from another country
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.
See Google Shopping price comparison for the query and the result fields.
The product prices recipe covers typed prices, fallback selectors and JavaScript-rendered stores.
When not to: if the store publishes a feed or an affiliate API, read that first. Scraping is for the stores that do not.
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.
Web data for other teams
FAQ
Can I monitor competitor prices with an API instead of a scraper?
How do I get the price shown in another country?
What happens when a store blocks scrapers?
Does Microlink alert me when a price changes?
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.