Skip to content
Screaming Data

Custom datasets from any public source

Name the source and the fields. We scope the dataset with you, build it, and deliver clean JSON on your schedule — through the API or to your webhook. Quoted per project.

Your fields, one schema

Typed, documented records — not HTML. Every record carries the fields you named, in the same shape on every run.

You specify

Source
Any public URL — a catalogue, listing, directory or marketplace
Fields
The attributes every record should carry
Schedule
Once, daily or hourly — as often as you need it
Delivery
REST API or webhook, as JSON
You receiveExample record
{
  "url": "https://example.com/p/electric-kettle-17",
  "observed_at": "2026-09-24T09:00:00Z",
  "name": "Electric Kettle, 1.7 L, Brushed Steel",
  "price": {"amount": 49.9, "currency": "EUR"},
  "in_stock": true,
  "rating": 4.6,
  "attributes": {"capacity": "1.7 L", "power": "2200 W"}
}

Sources we work with

Publicly available websites of every kind. A few examples:

  • Catalogues

    Products, specifications and prices from online shops and brand sites.

  • Listings

    Classifieds, property, jobs, events — any page that lists items.

  • Directories

    Companies, venues and locations, as structured records.

  • Marketplaces

    Offers, prices, ranks and ratings beyond the ready-made marketplace data.

How delivery works

The dataset is yours through the same REST API as everything else — no files to collect by hand, no format of its own.

  • Through the same API

    One login and key, the same response envelope as the marketplace endpoints, and the exact cost in every response.

  • Pushed to your webhook

    Every result posted to your endpoint as soon as it is ready, signed with HMAC-SHA256 and retried with back-off.

  • On your schedule

    Once, daily or hourly. Records keep the same shape on every run, so nothing downstream has to change.

The mechanics are the same as for the marketplace endpoints: response format and webhooks.

How an engagement works

  1. 01

    Describe the data

    The source, the fields, the schedule and a rough volume.

  2. 02

    Receive a written proposal

    Our data team scopes the dataset and replies with the fields, schedule, delivery and price.

  3. 03

    Receive the records

    JSON through the API or to your webhook, on the schedule you chose.

FAQ

Anything else? Write to sales@screamingdata.dev — a description of the source and the fields is enough to start.

How is a custom dataset priced?
Per project. The price depends on the source, the fields, the schedule and the volume, and the written proposal states it.
How is the data delivered?
As JSON records with the fields you named, through the REST API or pushed to your webhook, on the schedule you chose.
Which sources can you work with?
Publicly available websites. Tell us the source and what you need from it; the proposal says how we will deliver it — or why we cannot.

Describe your data.

A link to the source and the fields you need are enough to start.

Get a quote