Event Ticket Price Monitor
Pricing
from $10.00 / 1,000 tracked events
Event Ticket Price Monitor
Track ticket prices and availability for events from public event pages (schema.org Event/Offer). Structured JSON: event, venue, date, price range, currency, availability.
Pricing
from $10.00 / 1,000 tracked events
Rating
0.0
(0)
Developer
Technical Dost Solutions
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
a day ago
Last modified
Categories
Share
What this Actor does
Track ticket prices and availability for events from public event pages you supply.
It processes user-provided public event URLs, prioritizes JSON-LD/schema.org Event and Offer structured data (including MusicEvent, SportsEvent, and TheaterEvent), and can optionally run a conservative fallback price scan over visible page text. It normalizes useful fields, deduplicates rows, and saves structured records to the Apify dataset for recurring price monitoring.
Why this Actor is useful
Buyers pay for this kind of extraction when it saves manual checking, creates repeatable price monitoring, feeds spreadsheets or dashboards, and turns public event pages into clean API-ready datasets.
Who this is for
- Event resellers and brokers monitoring their own permitted listings
- Promoters and venues tracking public price signals
- Price-comparison and deal-alert builders
- Analysts and researchers studying public event pricing
- Fans tracking price/availability for events they follow
Common use cases
- Monitor ticket price ranges and availability over time
- Build price-comparison or deal-alert datasets
- Feed dashboards or spreadsheets with public event pricing
- Track availability status changes for events you follow
- Create recurring public event pricing snapshots
Input
startUrls: Public event page URLs to extract from. Use only pages you are permitted to access without login or bypassing access controls.maxItems: Maximum number of rows to save.maxConcurrency: Number of pages processed in parallel. The default is intentionally conservative.extractionMode: UsestructuredDataOnlyorstructuredDataWithFallback. The default enables a safe public price fallback when noEventstructured data is present.requestTimeoutSecs: Maximum time to spend on a single page.proxyConfiguration: Optional Apify proxy configuration where permitted by your source review.
Output
eventName: Event name from structured data or page title/heading.performer: Performer or act name when exposed in structured data.venue: Venue name from the event location.eventLocation: Event address or locality string.eventDate: Event start date/time.ticketPriceMin: Lowest ticket price found across offers.ticketPriceMax: Highest ticket price found across offers.currency: Price currency code such as USD, GBP, or EUR.ticketAvailability: Availability status such as InStock or SoldOut when published.ticketUrl: Ticket or offer URL, or the source page URL.platform: Hostname of the source page.sourceUrl: URL where the data was extracted.detectedAt: Timestamp when this Actor extracted the row.extractionMethod:structured_datafor valid Event/Offer schema, orfallback_price_scanfor visible public price text.confidenceScore: Heuristic confidence score based on structured data availability.missingFields: Output fields that were not available from the source page.
Sample input
{"startUrls": [{"url": "https://example.com/events/indie-night-live"}],"maxItems": 25,"maxConcurrency": 3,"extractionMode": "structuredDataWithFallback","requestTimeoutSecs": 30}
Sample output
{"eventName": "Indie Night Live","performer": "The Examples","venue": "Example Arena","eventLocation": "Boston, MA, US","eventDate": "2026-08-15T20:00:00-04:00","ticketPriceMin": 45,"ticketPriceMax": 150,"currency": "USD","ticketAvailability": "InStock","ticketUrl": "https://example.com/events/indie-night-live/tickets","platform": "example.com","sourceUrl": "https://example.com/events/indie-night-live","detectedAt": "2026-06-27T00:00:00.000Z","extractionMethod": "structured_data","confidenceScore": 0.95,"missingFields": []}
How to use
Run this Actor on Apify with public event URLs, export the dataset as JSON, CSV, Excel, or through the Apify API, then connect the output to Google Sheets, Make, Zapier, a webhook, or a dashboard. For price monitoring, save the input as an Apify task and schedule recurring runs.
Pricing
This Actor uses a pay-per-event pricing model: $0.01 per tracked event row saved to the dataset. You pay only for the normalized event rows the Actor produces.
Best practices
- Start with a small set of reviewed public event URLs.
- Prefer pages that expose schema.org
EventandOfferJSON-LD. - Use
structuredDataOnlywhen you want the highest precision and can tolerate empty output. - Use
structuredDataWithFallbackfor reviewed public pages that show visible prices but no Event schema. - Keep
maxConcurrencylow for smaller websites. - Review source website rules before scheduling recurring runs.
Compliance and responsible use
This Actor is for public data only. It must not be used to bypass logins, paywalls, CAPTCHAs, or security systems, collect private data, or support spam or abuse. Many ticket resale platforms (for example StubHub and Viagogo) use bot protection and have restrictive terms of service; this Actor is not designed to defeat those protections. It works on public event pages that expose Event/Offer JSON-LD and is intended for monitoring pages you are permitted to access. You are responsible for following applicable laws and source website rules.
Limitations
- Output quality depends on the public structured data available on the source pages.
- The fallback price scan is intentionally conservative; it derives a price range from visible currency-and-number patterns and infers a name from the title/heading. It does not claim universal event-page support.
- Many resale sites use bot protection and restrictive ToS and are not supported targets.
- Some fields may be empty when the source does not publish them.
- Website markup and access policies can change.
Troubleshooting
- Empty output usually means the page has no public
EventJSON-LD and no visible price text. - Invalid URL errors mean one or more input URLs are malformed.
- Slow runs can usually be improved by lowering
maxConcurrency. - Missing fields are source-data limitations, not inferred values.
Changelog
- v0.1.0: Initial release with Event/Offer structured-data extraction and conservative public price fallback.