Fourthwall Shop Products & Price Monitor
Pricing
from $2.00 / 1,000 core fourthwall products
Fourthwall Shop Products & Price Monitor
Export public Fourthwall shop products, variants, prices, stock, descriptions and images, or track reliable catalog changes with explicit coverage.
Pricing
from $2.00 / 1,000 core fourthwall products
Rating
0.0
(0)
Developer
Luka
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
๐ Start in 60 seconds
- Keep Collect current products selected.
- Paste one or more public Fourthwall shop URLs, including creator custom domains.
- Choose Detailed product rows for descriptions, brand, all images, and per-variant stock.
- Set Maximum products and Maximum buyer charge to the limits you want.
- Click Start and open the Dataset.
The default run exports up to 50 detailed products from Fourthwall's own public demo shop. No creator login, API key, Storefront token, account cookie, customer data, or order access is required.
{"workflow": "collect","shopUrls": ["https://shop.fourthwall.com"],"detailLevel": "detailed","maxProducts": 50}

๐ฏ Choose the right workflow
Collect current products returns one normalized row per unique public product. It is designed for creator-commerce research, assortment comparisons, price tracking, product-feed QA, and catalog exports.
Track product changes creates or compares a private baseline for the same targets, detail level, limits, and monitoring scope name. It reports NEW, UPDATED, and only after two complete comparable absences, ENDED.
Use exact product URLs when you need a small watchlist instead of a whole shop. Shop and exact-product targets can be combined in one run and are deduplicated by Fourthwall's stable public product ID.
๐ฆ What you get
Every product row can include:
- stable product and variant UUIDs;
- canonical shop and product URLs, including custom domains;
- product title, handle, description, brand, and product-level SKU;
- current and compare-at price with currency;
- product and per-variant availability;
- every public variant title, price, currency, availability, and link;
- primary image and all public product images;
- source-published creation and update timestamps;
- explicit detail and coverage status.
The mixed Dataset also contains one free coverage row. Monitoring runs return deterministic change rows with before/after snapshots and the exact fields that changed.
๐๏ธ Input guide
- Fourthwall shop URLs accepts normal Fourthwall subdomains and creator custom domains.
- Exact product URLs accepts public
/products/...pages. - Detail level chooses a low-request catalog export or one public detail request per product.
- Maximum products, Maximum products per shop, Maximum catalog pages, and Maximum detailed products bound work and output.
- Monitoring scope name separates independent baselines. Keep it unchanged for comparable repeat runs.
- First monitoring run either seeds silently or returns every current product as
NEW. - Maximum buyer charge is a hard preflight guard, not a spending target.
๐ฐ Pricing
This Actor uses pay-per-event pricing. Failed and blocked targets produce no paid product rows and never advance monitoring state.
| Delivered value | Free-tier price |
|---|---|
| Verified public shop or exact-product target | $0.0025 |
| Core catalog product | $0.002 |
| Detailed product | $0.003 |
| Comparable monitoring target | $0.003 |
| Delivered product change | $0.002 |
Core and Detailed product prices are mutually exclusive. A 100-product Detailed export from one shop is $0.3025 before Apify platform usage; the same Core export is $0.2025. Your input charge guard can stop the run before source work begins.
โ Coverage you can trust
Each run reports one of these states:
COMPLETE: every requested public target was exhausted within your limits;CAPPED: a product, page, request, transfer, or runtime limit stopped full traversal;PARTIAL: useful results were returned, but at least one target failed or was blocked;BLOCKED: the public target denied access; it is not called empty;FAILED: the expected Fourthwall public product contract was not reached;EMPTY_CONFIRMED: the expected public surface loaded and explicitly contained no products.
Only COMPLETE and EMPTY_CONFIRMED coverage can update monitoring state or advance a missing product toward ENDED. Duplicate products from overlapping shop and exact-product inputs are merged before billing.
๐ API and automation
Run the Actor from Apify Console, API, CLI, Make, Zapier, Google Sheets, webhooks, or another Apify integration. The Dataset is exportable as JSON, CSV, Excel, XML, RSS, or HTML.
For monitoring, use the same saved input and stateNamespace on repeat runs. Scheduling and downstream notification delivery are handled through Apify's standard automation surfaces; this Actor does not ask for third-party webhook secrets or email credentials.
โ ๏ธ Not yet supported
- private, hidden, archived, login-only, or password-protected products;
- creator dashboard analytics, orders, customers, memberships, or payouts;
- discovery of all Fourthwall creators or shops from a keyword;
- arbitrary collection-handle selection beyond the complete public
allcatalog; - shipping quotes, taxes, checkout actions, or cart mutation;
- guaranteed stock quantity when Fourthwall publishes only availability.
Secondary fields such as compare-at price, product-level SKU, brand, and timestamps remain null when a public shop does not publish them.
โ FAQ and support
Does it need a Fourthwall token? No. It uses only public shop surfaces Fourthwall documents for public product integration.
Do custom domains work? Yes, when the domain serves the verified Fourthwall public catalog contract. MKBHD and New York Magazine custom-domain shops are part of the source test set.
Why did my run say CAPPED? A declared input or safety limit was reached. Narrow the shop set or raise the relevant limit and buyer-charge guard deliberately.
Can a temporary failure remove products from my monitor? No. Blocked, failed, partial, or capped runs do not infer removal. ENDED requires two complete comparable misses.
For a reproducible issue, share the public shop or product URL, workflow, detail level, coverage status, and run ID. Never share login credentials, cookies, private tokens, customer data, or order data.