Thomann Scraper
We do not have a dedicated Thomann data API. What we do have is an AI scraper that reads a thomann.de page you point it at, turns it into the columns you asked for and hands them back by REST, CSV or Excel — on a schedule, priced per page.
- thomann.de
- thomann.co.uk
How to scrape Thomann
Thomann publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface. Thomann is the European music retail price reference and sells into every EU market from one catalogue. The way to get the data is to read the page the way a customer sees it: point the AI scraper at a thomann.de URL, declare the columns you want in plain English, and schedule it. Specialist retailers compete on range and expertise rather than on headline price, so availability and specification carry as much signal as the number.
What the AI scraper does with a thomann.de link
The same three steps as any other page you point it at. Nothing about Thomann is pre-built, which is exactly why it works on pages nobody wrote a connector for.
Paste the link
Give it a thomann.de product or listing URL. Market, currency and assortment all come from the page itself, so there is no region setting to get wrong — the URL decides.
Declare the columns
Name each field, give it a type and write a line telling the AI what to look for. “brand” and “product_title” are the two most people start with. The schema is yours and you can change it between runs.
Schedule it and collect
Run it hourly, daily or on demand. Every run returns the same columns in the same order with a timestamp on each row, so the history builds itself.
Set it up once. The data keeps coming.
Save your search once and it runs by itself. Every run lands in your own Scrapewise database, and you pick how to read it.
Set it up once
Add your ASINs, keywords, places or apps to a scraper in the web app. New accounts get 5 free requests.
Runs on your schedule
Pick daily, weekly on the days you choose, every few days, or the first or last day of the month. Scheduled runs start at night, European time. Need it more often? Start runs from your own code.
Saved in your database
Each run adds dated rows, so this week sits next to last week. Rows are kept for 90 days.
Use it your way
Open the table in the web app and download the latest run as an Excel file. Ask your own AI assistant about it. Or pull the rows into your code with an API key.
Ask your AI assistant about your own data
Connect Claude Desktop or Claude Code with a read-only key. The assistant reads the rows you've already collected, at no extra cost on Scrapewise. With a full-access key it can start a run for you too.
- Which of my ASINs lost the Buy Box this week?
- Which competitor cut prices the most since Monday?
- Show the keywords where I dropped out of the top 10.
What you send and what you get
You send a link and a column list. Everything else — market, currency, which products are on the page — comes from the page, so there is nothing to configure twice.
- Link to a Thomann pagerequired
Open the product or category page in your browser and copy the address. Any Thomann country domain works the same way.
https://www.thomann.de/ - Your column listrequired
Field name, type and one line of plain English per column. Written once, reused on every run.
brand, product_title, sku, price - How often it runsoptional
Hourly, daily, weekly or on demand through the API. Daily is what most price monitoring uses.
Daily at 06:00 UTC
One row per product on the page, 12 columns each
- brand
- product_title
- sku
- price
- was_price
- currency
- availability
- delivery_estimate
- rating
- review_count
- product_url
- checked_at
REST API, CSV or Excel. The column set stays the same between runs, so downstream jobs do not re-map fields.
The columns a Thomann run comes back with
We are not going to print a table of invented hobby and specialist prices and call it real output. Thomann answers an ordinary request with Cloudflare rather than a product page, so we have no run of our own to quote from. So what is published here is the column list you declare before the run, which is the same list every run comes back with.
brandBrand as the site labels itproduct_titleProduct title as the site writes itskuSite's own article numberpricePrice the site is charging todaywas_priceStrike-through price, only where the page shows onecurrencyCurrency the page quotedavailabilityStock state as the page states itdelivery_estimateDelivery window shown on the pageratingAverage rating, where shownreview_countHow many reviews back that ratingproduct_urlLink back to the page the row came fromchecked_atWhen this run collected the page (UTC)Every column here is one you name yourself in the schema. If a field is not on the page on the day of the run, it comes back empty rather than guessed.
What a Thomann page costs
Pay-as-you-go from your wallet. No plan, no monthly fee, no seat count.
Measured on 3 October 2026, not assumed. A plain request for a thomann.de page returns a document rather than a refusal, but Cloudflare is in front of it, and the parts of the page that carry price are filled in by JavaScript after load, so a browser is what makes the run reliable.
500 Thomann pages checked once a day for a month is 15,000 pages.
about EUR 22.50 for the month
You are charged for what a run actually used, not what it was expected to need, and your balance never expires.
See the full price list →What this page is not promising
We would rather say this here than in a support ticket.
No dedicated Thomann endpoint
There is no Thomann API in our catalogue and no pre-built Thomann schema. The AI scraper reads the page you point it at — that is the whole mechanism, and it is why it works on pages nobody built a connector for.
Nothing behind a login
It reads what a visitor can see. Account pricing, contract pricing and anything behind a sign-in are out of scope.
No field the page does not show
If the page does not print it, the scraper cannot return it. Identifiers like EAN or GTIN only come back where the retailer publishes them.
A price is a point in time
Every row carries the timestamp of the run that collected it. A price without one is not evidence, which is why the column is in the default schema.
Thomann has one specific trap
B-stock units are listed separately with their own condition grade and price under the same product.
Not a bulk dump of the catalogue
You give it the URLs you care about. It does not crawl thomann.de end to end, and a schedule that tried to would cost more than the answer is worth.
Typical fields the AI scraper extracts from a Thomann page
Treat this as a starting point rather than a fixed schema. What comes back is whatever the page actually shows on the day of the run.
Price and promotion
Specialist pricing moves less often than mass retail, which makes each move more informative.
- Current price
- Strike-through or was-price where shown
- Promotion or bundle wording as printed
- Trade-in or finance offer text, where the page prints it
- Currency the page quoted
Range and availability
In a specialist category, carrying the item at all is a competitive position.
- Stock state as the page states it
- Delivery window shown
- Whether the item is special order, where stated
- Backorder or pre-order wording
- Which variants are listed at all
Specification and identity
Specialist buyers compare on specification, and the specification is usually rendered as a table.
- Brand and model name
- Site's own article number
- Manufacturer part number, where printed
- Technical specification table, where rendered
- Category breadcrumb
- Rating and review count, where shown
The column list is one you write: name each field, give it a type and a line telling the AI what to look for. The schema belongs to your run, not to us. How Custom Schema works →
What it cannot give you If a field is not visible on the page, the scraper cannot invent it. Identifiers such as EAN or GTIN only come back when Thomann publishes them.
What people use Thomann data for
Price and availability tracking on a narrow range
In a specialist category a few hundred SKUs is the whole competitive set, which makes this one of the cheapest scrapes to run and the easiest to act on.
Range and gap analysis
Which models a competitor actually carries, and which they have dropped. In specialist retail that is the strategic question.
Brand price-floor checks
If you make specialist equipment, this is how you see what your models are actually listed at across the dealers that carry them.
Promotion and bundle tracking
Specialist retailers discount through bundles and trade-ins rather than headline cuts, and that is text on the page.
Cross-retailer specification comparison
Where pages publish part numbers and specification tables, one schema across dealers produces a table that joins.
Feeding your own pricing rules
The export is a normal REST API or CSV, so it drops into whatever pricing logic you already run.
What makes Thomann harder than an ordinary storefront
Here is what the scraper is actually up against on thomann.de, measured rather than assumed.
Access
- Plain HTTP requests are answered, but the answer is the shell of the page rather than the priced version of it
- Named protection on the response: Cloudflare
- robots.txt carries a blanket disallow, so the scheduling decision is yours to make and document
Narrow range, deep detail
- The interesting data is in the specification table rather than in the price, and specification tables are rendered differently on every site
- Bundles and trade-in offers change the real price without changing the number
- Special-order and backorder states are not the same as out of stock, and the page wording is the only way to tell
- Product pages are detail-heavy, so a rendered page is often required rather than optional
What the page publishes
- Structured data is published but not at product level (ContactPoint, Organization, PostalAddress), so price comes from the rendered page rather than a feed
- B-stock units are listed separately with their own condition grade and price under the same product.
- Price is one of the last things the page settles on, so a read taken too early records the placeholder rather than the number
Keeping a history
- A single read is a snapshot; the value is in the series, which means the run has to be scheduled and the rows kept
- Every row carries the timestamp of the run that produced it, so two days can be compared without guesswork
- Columns stay stable between runs, so a dashboard written once does not break when the site redesigns
Thomann scraping — questions
What people ask before pointing the scraper at thomann.de.
Thomann publishes no read API for its catalogue. There is no key to apply for and no endpoint to call, which is why the page is the interface.
Ready to pull Thomann data into your stack?
Start free — or talk to our team about your exact fields, refresh cadence and volume.