datawebotThe product data behind the storefront.
Turn a store, collection or product URL into structured records you can work with. Choose the scope. Review the cost. Keep the output.
| Variant | SKU | Example price | Example availability |
|---|---|---|---|
| Small / Navy | DEMO-TEE-S-NV | USD 32.00 | Example: available |
| Medium / Navy | DEMO-TEE-M-NV | USD 32.00 | Example: available |
| Medium / Sand | DEMO-TEE-M-SD | USD 34.00 | Example: unavailable |
| Large / Navy | DEMO-TEE-L-NV | USD 32.00 | Example: unknown |
All names, identifiers, prices and availability values are fictional. They do not describe a merchant’s catalog or inventory.
Built for the structure of ecommerce.
A price belongs to a variant. An identifier belongs to a source. A collection contains products that may each have several sizes, colors or configurations.
datawebot. retrieves the structured records exposed by a store and preserves those relationships in a consistent output.
Explore the data schemaIdentifiers, title, vendor, product type, description and image links where provided.
Identifiers, SKU, named options, prices, compare-at prices and observed availability.
Source URL, retrieval time, currency, warnings and completeness information.
Readable product tables, CSV exports and paginated JSON through the API.
Three useful starting points.
Input and scope guideProduct
One product URL returns the product and its reported variants. A variant selection in the URL does not restrict the result to that variant.
Collection
A collection URL keeps the request scoped to that collection. Set a page budget and choose which pages to follow.
Catalogue
A store URL reads its accessible product catalogue within your page budget. Completeness describes the accessible feed, not a merchant's private inventory.
Browse source guides.
Review fields and source-specific context before choosing an input.
Your request stays with you.
Some extractions finish quickly. Others take longer. Every request has a saved ID, a spending limit and a place in your history.
Processing and resultsYour request is saved. Return for updates or act on a request for confirmation.
Inspect the output, check any completeness notes and download your data.
Read the explanation and credit outcome when a request needs a different retrieval path.
A few useful answers.
Start with a store URL.
Get the product data you need for whatever comes next.