From URL to useful data.
Start in the browser or connect your code. The same request, result and credit model applies to both.
Start with the job you need to finish
Your first extraction
Start your first datawebot. ecommerce extraction from a store URL, set a bounded scope, inspect the result and download CSV or JSON.
Start hereURLs and extraction scope
Learn how product, collection and catalogue URLs determine datawebot. extraction scope, page traversal, markets, variants and returned records.
ConceptsProcessing and results
Learn how saved datawebot. extraction requests continue across sessions, move through processing states and report completeness or required action.
ConceptsProducts, variants and fields
Review the datawebot. product and variant data schema, including source identifiers, prices, availability, images and record relationships.
ConceptsCSV and JSON exports
Compare datawebot. CSV and JSON exports for spreadsheets, applications and agents, including file structure, pagination and retention details.
AccountCredits and billing
Understand how datawebot. credits cover ecommerce source pages visited and processed, including discovery, budgets, failed visits and top-ups.
DevelopersAPI quickstart
Follow the datawebot. API quickstart to submit an ecommerce extraction, save its request ID, monitor processing and retrieve the final output.
DevelopersAPI reference
Review the authenticated datawebot. HTTP API for creating ecommerce extractions, checking request status and retrieving structured results.
DevelopersConnect your agent
Learn how agents can submit saved ecommerce extraction requests, enforce credit budgets, monitor status and retrieve structured data safely.
AccountTroubleshooting
Troubleshoot datawebot. sign-in, URL validation, extraction processing, incomplete results, credit budgets and file downloads without losing saved work.