Brand, category and product data
Returns the core Very page record: title, brand, category path, images and description. Use it to audit a broad catalogue spanning fashion, home, furniture, electricals and toys, and to map listings to your own.
Pull Very listings as JSON: product code, brand, price in GBP, previous price, payment options, specifications, ratings and stock status. One REST call replaces proxies and parsers, so you can follow UK prices across fashion, furniture, electricals and toys and spot offers as they change.
# Request (replace the key and URL with your own)
POST https://api.webfusiondata.com/v1/product
Authorization: Bearer $WFD_API_KEY
{ "url": "https://www.very.co.uk/example-smart-tv/EXAMPLE123.prd",
"country": "GB" }
# Response (sample data, not a live listing)
{
"product_code": "EXAMPLE123",
"marketplace": "GB",
"title": "Example Smart TV, 50 inch",
"brand": "Example Brand",
"price": { "amount": 399.00, "currency": "GBP" },
"availability": "Available",
"rating": 4.5,
"product_url": "https://www.very.co.uk/example-smart-tv/EXAMPLE123.prd"
}
Sample values for illustration only. Exact field names and nesting for your Very scope are confirmed in the API reference issued with your key.
A Very UK Product Data API turns very.co.uk product pages into records your systems can use. Send a product link or a keyword and get JSON with brand, title, price, previous price, specifications, rating and stock status. Each response follows one schema, so the data loads straight into price trackers, dashboards and catalogue systems.
We run the collection layer: managed proxies, page rendering, Very-specific parsing and field validation happen before a response is returned. Large jobs run in the background and arrive by webhook or cloud export, so your integration stays a few HTTPS calls.
Fashion, furniture and electronics brands, retailers and price analysts use Very data to benchmark prices across a broad catalogue, follow sale periods and offers, compare specifications with rival listings and watch stock. Our price monitoring and price intelligence services build on the same data.
From choosing what to collect to loading it into your own systems, in six steps.
Choose one product page, a batch of product URLs built from your code list, or a keyword or category search on very.co.uk.
List the fields you need, such as price, previous price, payment options or stock status, so they can be checked against the pages.
Build a JSON body with url (or site and query) and an optional country.
Pick /v1/product for one item, /v1/search for result lists, /v1/monitor for scheduled tracking or /v1/bulk for batches.
Send your API key as a bearer token in the Authorization header.
Use the sandbox first; it returns sample responses and uses no live request credits.
We open the Very page, render it, extract the fields and validate them. Single lookups answer in the same request.
Bulk jobs give you a job ID to check at /v1/status/:job_id or to receive by webhook.
JSON is the default, and bulk exports can be delivered as CSV or XLSX.
Every record has a crawled_at timestamp, so each price and stock status comes with its capture time.
Write results to a database, update a BI dashboard, raise alerts from webhooks or run recurring checks with monitors.
The Integration and Data Delivery section includes a worked example.
What the Very UK Product Data API does for pricing and category teams, and which parts are documented today versus settled per project.
Returns the core Very page record: title, brand, category path, images and description. Use it to audit a broad catalogue spanning fashion, home, furniture, electricals and toys, and to map listings to your own.
Each product is reached by its page URL, so a list of product pages becomes a list of requests to /v1/product. The product code shown on the page is returned in each record for matching.
Captures the current price in GBP and, where shown, the previous price and saving. Register a page for scheduled checks with a webhook on change to run a Very price monitoring API workflow through sales and seasonal events.
Where a page shows a payment option, such as a weekly or monthly price, the displayed text is returned with the record. Credit terms and eligibility are not shown to anonymous visitors, so they are out of scope.
Returns the specifications and product details shown on the page, which supports like-for-like comparison of electricals, furniture and appliances with other UK retailers.
Returns the star rating and review count shown on each listing, so you can compare products by customer feedback. Review text is confirmed per project.
Returns the stock status and the delivery options shown on the page, where displayed. Postcode-specific delivery and charges are confirmed per project.
The country parameter sets the marketplace for each request. For Very the starting point is the UK site, very.co.uk, and any other scope is confirmed at onboarding.
Use recurring monitors, webhook callbacks or bulk exports to cloud storage, with type-checked JSON, so fresh data arrives without manual pulls.
The fields our Very product data extraction can return, what each one means and how pricing teams use it. Availability follows what each page displays.
| Data Field | Description | Business Application | Availability |
|---|---|---|---|
product_code | Product code shown on the page or in the URL | Product identification, de-duplication | Core |
title | Product name as listed | Catalogue management, content checks | Core |
brand / category | Brand and category path shown on the page | Brand share analysis, category benchmarking | Core |
price.amount / price.currency | Current price and its currency (GBP) | Price comparison, repricing inputs | Core |
discount | Previous price and saving when shown | Sale and reduction analysis | Where displayed |
payment_options | Payment option text shown on the page | Affordability messaging comparison | Confirm at onboarding |
specifications | Specifications shown on the page | Like-for-like product comparison | Where displayed |
rating / review_count | Star rating plus review count | Product research, quality comparison | Where displayed |
availability | Displayed stock status | Out-of-stock alerts, availability monitoring | Core |
delivery | Delivery options shown on the page | Fulfilment comparison | Confirm at onboarding |
images | Product image URLs shown on the page | Catalogue enrichment, visual checks | Core |
product_url / crawled_at | Page URL and capture timestamp | Reference, freshness checks, time series | Core |
Core = part of the standard field set on our ecommerce API. Where displayed / available / exposed = returned when the listing on that marketplace shows it, so it can be empty for some products. Confirm at onboarding = settled per project. Images and product detail text are also returned. Field names are illustrative; your API reference is the source of truth.
The Very UK Product Data API uses the same versioned endpoints as the Ecommerce Scraping API. Very-specific parameter names that are not yet published are marked as illustrative.
| Endpoint | Purpose | Parameters | Expected response |
|---|---|---|---|
POST /v1/productDocumented |
One Very product returned as structured data: GBP price, previous price, specifications, rating and availability. | Required: urlOptional: country; a dedicated product_code field is a confirm |
One JSON product record, returned synchronously. |
POST /v1/searchDocumented |
Keyword or category search on very.co.uk, returned as a structured result list. | Required: site (e.g. "very"), queryOptional: country |
JSON with query, result_count and a results array. |
POST /v1/monitorDocumented |
Registers a listing for scheduled price and stock monitoring with webhook notifications. | Required: urlOptional: webhook URL and check frequency names: confirm |
A monitor ID you use to read tracked data later. |
GET /v1/monitor/:idDocumented |
Latest tracked data and change history for one monitored product. | Required: id (path) |
JSON with the current values and recorded changes. |
POST /v1/bulkDocumented |
Submits a batch of URLs for asynchronous processing; results go to storage or a webhook. | Required: list of URLs Optional: delivery destination and format (JSON, CSV or XLSX) names: confirm |
A job ID, then results via webhook or storage export. |
GET /v1/status/:job_idDocumented |
Status and progress of an asynchronous crawl or bulk export. | Required: job_id (path) |
JSON with job state and progress. |
| Situation | Typical HTTP status | How to fix it |
|---|---|---|
Missing or malformed url | 400 | Send the full Very product URL, including https://. |
| Unsupported site or country value | 400 / 422 | Check site and country against the marketplaces confirmed for your account. |
| Missing or invalid API key | 401 | Send Authorization: Bearer <key> and check the key belongs to the right environment (sandbox or live). |
| Listing not found or no longer available | 404 or an empty record | Check the URL; products can be removed once a line ends. |
| Request limit exceeded | 429 | Wait, then retry with backoff. Response headers show your remaining quota for the window. |
| Temporary processing failure | 5xx | Retry with exponential backoff; for large volumes use /v1/bulk instead of many synchronous calls. |
Status codes follow common REST conventions (429 is the one shown in our published dashboard example). The exact codes and error bodies are listed in the API reference supplied with your key.
Two common calls and what comes back. Illustrative sample data — not live product information.
curl -X POST https://api.webfusiondata.com/v1/product \
-H "Authorization: Bearer $WFD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"url": "https://www.very.co.uk/example-smart-tv/EXAMPLE123.prd",
"country": "GB"
}'
curl -X POST https://api.webfusiondata.com/v1/search \
-H "Authorization: Bearer $WFD_API_KEY" \
-d '{"site": "very", "query": "sofa", "country": "GB"}'
url or site + query select what to fetch; country selects the marketplace. The key stays in an environment variable — never hard-code it or ship it in client-side code.{
"product_code": "EXAMPLE123",
"marketplace": "GB",
"title": "Example Smart TV, 50 inch",
"brand": "Example Brand",
"price": { "amount": 399.00, "currency": "GBP" },
"discount": { "percent": 20, "list_price": 499.00 },
"availability": "Available",
"rating": 4.5,
"review_count": 215,
"seller": "Example Seller",
"product_url": "https://www.very.co.uk/example-smart-tv/EXAMPLE123.prd",
"crawled_at": "2026-01-15T09:30:00Z"
}
{
"query": "sofa",
"result_count": 48,
"results": [
{ "title": "Example Smart TV, 50 inch", "price": 399.00,
"rating": 4.6, "in_stock": true }
]
}
The generic search sample on our Ecommerce Scraping API page uses a flat price number and an in_stock flag, while the product example above nests price under an object. The final Very schema is confirmed in your API reference.
Choose the marketplace with the country parameter. We do not claim global coverage: the marketplaces available to you are confirmed during onboarding, and requests outside that list are rejected rather than guessed.
| Marketplace | Very domain | Local currency | Status for the API |
|---|---|---|---|
| United Kingdom | very.co.uk | GBP | Confirm at onboarding |
This is the site we plan around, not a coverage guarantee. Need anything else? Tell us and we will confirm feasibility.
Why it matters: the site fixes the currency (GBP), the range and which optional fields (previous price, payment options, delivery) appear. Delivery options can depend on the postcode, so tell us if you need location-level data.
What is published today, and what we give you in writing before you go live. We do not publish numeric limits, latency or uptime figures on this page.
| Topic | How it works | Status |
|---|---|---|
| Authentication | Your API key is sent as a bearer token in the Authorization header. Use the sandbox key while testing. | Documented |
| Limits and concurrency | Per-minute limits and concurrent-request allowances scale with your plan; response headers show your remaining quota. Use /v1/bulk for very large volumes. | DocumentedNumbers: your plan |
| Validation and errors | Malformed or missing parameters are rejected with a standard HTTP error (see Endpoints), and responses are schema-checked before delivery. | Exact codes: API reference |
| Timeouts and retries | Set a client timeout and retry reads on 429 and 5xx with exponential backoff. Move long work to /v1/bulk and /v1/status/:job_id, and avoid blind retries of POST /v1/monitor or /v1/bulk. | Recommended practice |
| Pagination | Search returns a result_count and result list. Pagination for deeper results is scoped per project. | Confirm at onboarding |
| Usage monitoring | An account dashboard shows request volume, latency, success rate and job status. | Documented |
A Very API integration needs a request layer, somewhere to store results and a schedule. The data can then feed pricing tools, databases, BI dashboards, reports and analytics pipelines.
Agree marketplaces, fields and refresh frequency, then call the sandbox with a few sample products.
Put authentication, timeouts and retry backoff in one small client module your whole team reuses.
Upsert records by product code and marketplace, and keep every crawled_at timestamp to build a time series.
Use monitors and bulk jobs, act on webhooks, and connect the table to your dashboards and reports.
import os, sqlite3, requests
API = "https://api.webfusiondata.com/v1/product"
HEADERS = {"Authorization": f"Bearer {os.environ['WFD_API_KEY']}"}
def fetch(path):
body = {
"url": f"https://www.very.co.uk/{path}",
"country": "GB",
}
r = requests.post(API, json=body, headers=HEADERS, timeout=60)
r.raise_for_status()
return r.json()
db = sqlite3.connect("very_prices.db")
db.execute("CREATE TABLE IF NOT EXISTS prices "
"(product_code TEXT, amount REAL, currency TEXT, at TEXT)")
for path in ["example-smart-tv/EXAMPLE123.prd"]:
item = fetch(path)
db.execute("INSERT INTO prices VALUES (?, ?, ?, ?)", (
item["product_code"],
item["price"]["amount"],
item["price"]["currency"],
item.get("crawled_at"),
))
db.commit()
Default response format for every endpoint.
Bulk export jobs delivered as CSV or XLSX to S3, GCS or your own bucket.
Callbacks when a job completes or a tracked value changes, plus recurring checks through /v1/monitor.
Managed warehouse connectors, client libraries and no-code paths.
Listed on the Ecommerce Scraping API page; availability for your Very scope is confirmed during onboarding. See also the AI Parser and ecommerce datasets. Related: product availability and MAP monitoring.
A REST API from WebFusion Data that returns very.co.uk product pages as structured JSON. Send a product URL, or a keyword and a marketplace, and receive brand, title, GBP price, previous price, specifications, rating and availability. It shares endpoints with our Ecommerce Scraping API, so you never run proxies, browsers or parsers.
Core fields are product code, title, brand, category, price in GBP, availability, images, product URL and a capture timestamp. Previous price, specifications, rating and review count come back where the page shows them. Payment options, delivery options and review text are confirmed per project. See the data fields table.
Through the product URL, yes. Send each product page URL to /v1/product and the product code shown on the page is returned in the record for matching. Whether a dedicated code parameter exists, or whether codes can be resolved to URLs for you, is confirmed at onboarding.
Yes. POST /v1/monitor registers a product for scheduled price and stock checks with webhook alerts, and GET /v1/monitor/:id returns current values and recorded changes, which suits sale tracking. History starts at registration, so ask about a backfill or store each response with its crawled_at timestamp.
Payment options are returned only as the page displays them, for example a weekly or monthly price. Credit terms, eligibility and account-specific offers are not public page data, so they are not part of the API. We confirm the exact scope with you before you build on it.
We do not claim wide coverage. The country parameter selects the marketplace, and the UK site, very.co.uk, is the starting point. Tell us what you need and we will confirm it at onboarding. See the supported storefront.
Each request carries your API key as a bearer token in the Authorization header. Every account includes a sandbox for testing with sample responses. Keep the key on your server, in an environment variable or secrets manager, and never in client-side code.
JSON is the default for all endpoints. Bulk export jobs can also be delivered as CSV or XLSX, to S3, GCS or your own bucket. Webhooks, SDKs and database push options are described in Integration and Data Delivery.
Use the Request API Demo button or the form below and tell us the marketplaces, product volume, fields, refresh frequency and delivery format you need. We confirm the scope and set up access, including the sandbox. You can also email sales@webfusiondata.com or book a consultation.

At WebFusionData, we specialize in cutting-edge web scraping solutions to help you unlock valuable insights and drive business growth. Whether you need custom data extraction, real-time monitoring, or large-scale web scraping, our team is here to assist you.
Ready to get started? Contact us for a personalized quote.