zatista-scraper

Scrapes artist profiles and original artworks from Zatista.com, a US-based curated original-art marketplace — via the site's own product search API, no login required.

Contents

• Key features
• Output
• Input
• Input examples
• Incremental (delta) mode
• How to scrape Zatista.com
• FAQ

🔑 Key features

• Two entity types, one Actor. Set entityType to artworks or artists.
• A genuine sold/unsold split. Every artwork carries a real sold flag, and every artist rollup includes exact for_sale_count/sold_count/total_artworks — computed from two cheap count queries per artist, not a full per-artwork fan-out.
• Real bio data. Artist records include location, artist statement, education, professional experience, exhibitions, and artistic influences — genuinely server-rendered on the artist's own page, not a marketing summary.
• Full descriptions on every artwork, fetched from the artwork's own detail page.
• Delta mode built in. Every run classifies each item as new, changed, unchanged, or delisted against a persisted baseline.
• maxItems defaults to 50 — a fast preview, and what keeps an unconfigured run within Apify's automated 5-minute QA check. Zatista's real catalog is substantial (~29,000 for-sale + ~38,700 sold artworks) — clear maxItems (null) for a full run.

📋 Output

One dataset item per artwork or artist, depending on entityType — see .actor/dataset_schema.json for the full field list, or the Output tab's Artworks / Artists views for a readable table.

Example artwork record:

{
  "source": "zatista",
  "entity_type": "artworks",
  "external_id": "64427",
  "url": "https://www.zatista.com/product/details/64427/In-Between-Raindrops",
  "title": "In Between Raindrops",
  "artist_id": "6333",
  "artist_name": "Nestor Toro",
  "artist_slug": "nestor-toro",
  "artist_url": "https://www.zatista.com/artist/nestor-toro",
  "type": "Painting",
  "medium": "Acrylic",
  "medium_detail": "Acrylic on Canvas",
  "price": 21000,
  "currency": "USD",
  "sold": false,
  "total_quantity": 1,
  "height": 70.0,
  "width": 60.0,
  "unit": "in",
  "description": "BOLD Statement Work! This painting conveys motion and energy...",
  "image_url": "https://d1o22ltncixott.cloudfront.net/...",
  "change_type": "new"
}

Example artist record:

{
  "source": "zatista",
  "entity_type": "artists",
  "external_id": "6333",
  "url": "https://www.zatista.com/artist/nestor-toro",
  "name": "Nestor Toro",
  "slug": "nestor-toro",
  "location": "West Hollywood, CA United States",
  "bio_summary": "...",
  "for_sale_count": 863,
  "sold_count": 781,
  "total_artworks": 1644,
  "change_type": "new"
}

🔧 Input

Field	Type	Default	Description
entityType	string	artworks	artworks or artists.
maxItems	integer	50	Stop after pushing this many items. Set to null for a full crawl.
mode	string	auto	auto / full / incremental — see Incremental mode.
concurrency	integer	10	How many product/artist pages to fetch in parallel (validated live up to 25, no blocking).
impersonate	string	chrome	curl_cffi TLS-impersonation target.
proxyConfiguration	object	off	Apify Proxy config — not needed; no anti-bot friction found.

📥 Input examples

Default preview (50 artworks):

{ "entityType": "artworks" }

Full artist directory:

{ "entityType": "artists", "maxItems": null }

Full artwork catalog (for-sale and sold):

{ "entityType": "artworks", "maxItems": null }

🔁 Incremental (delta) mode

auto mode does a full scan the first time it runs for a given entityType, then only pushes new/changed items on later runs. Only an uncapped run (no maxItems limit reached) can detect delistings, sold-status changes, or price changes, or update the baseline.

🌐 How to scrape Zatista.com

Zatista's own artist-page and search widgets call a plain JSON endpoint (/old_search/searchProducts) — this Actor replicates exactly those calls, the same requests your own browser makes when you browse the site, just automated and exhaustive. There's no public artist directory, so both entity types discover their scope by walking this same endpoint across its for-sale and sold catalogs.

❓ FAQ

Is the sold/unsold split real, or estimated? Real — every artwork record's sold field and every artist's for_sale_count/sold_count come directly from Zatista's own for-sale and sold catalogs, not inferred.

Why is subject_id a number instead of a category name? Zatista's search API resolves type/medium to readable text (e.g. "Painting", "Acrylic") but not subject_id — no equivalent mapping was found, so it's passed through as Zatista's own raw internal code rather than guessed at.

Does this cover Zatista's Canada/UK/Australia/Ireland/New Zealand sites? No — this Actor scrapes zatista.com (USD pricing) only. The other-country storefronts share the same underlying catalog and artist ids but weren't built into this first version.

Does this need a proxy? No — no anti-bot friction was found anywhere on this site. Cloudflare sits in front, but a plain request with a normal browser User-Agent passes cleanly (tested at concurrency 25, zero blocking).