Ticketing display based on historical ticket database
The method fetches and stores ticketing information from online marketplaces to generate a subset for display in a dashboard, addressing the lack of automated historical databases in event management systems, improving ticketing information accessibility and management.
Patent Information
- Authority / Receiving Office
- HK · HK
- Patent Type
- Applications
- Current Assignee / Owner
- EAGLEANALYTIX
- Filing Date
- 2026-04-29
- Publication Date
- 2026-07-17
AI Technical Summary
Existing systems lack an efficient and automated method for creating a historical database of ticketing information from online marketplaces, which is essential for event management and ticketing services.
A method is developed to fetch and store ticketing information from online marketplaces at preset intervals, generate a subset based on client input, and display it in a dashboard interface.
Enables the creation of a comprehensive historical database for event management, enhancing ticketing information accessibility and management efficiency.
Smart Images
Figure 00000000_0000_ABST
Abstract
Description
This method involves creating a historical database of ticketing information by fetching and storing a set of ticketing information for a specific event from at least one online ticketing marketplace. The fetching and storing steps can be repeated at preset time intervals. The method then generates a subset of the event's ticketing information based on input from a client device. The method further includes displaying the generated subset of ticketing information. In some examples, this subset of ticketing information is displayed in a dashboard interface.
Claims
CLAIMSWhat is claimed is:
1. A method comprising:(a) scraping, by a server, an online ticket marketplace for a set of ticket information relating to an event;(b) storing, by the server, the set of ticket information; generating, by the server, a historical database of ticket information for the event by repeating steps (a) and (b) on a predetermined interval; based on an input from a client device, generating, by the server, a subset of ticket information for the event from the historical database of ticket information for the event; and displaying the subset of ticket information.
2. The method of claim 1, further comprising: displaying the subset of ticket information on a webpage of the online ticket marketplace relating to the event.
3. The method of claim 1, further comprising: displaying a representation of the subset of ticket information on a webpage of the online ticket marketplace relating to the event.
4. The method of claim 1 , wherein displaying the subset of ticket information on the webpage comprises overlaying a representation of the subset of ticket information within the webpage.
5. The method of claim 1, wherein the set of ticket information comprises: a number of a plurality of tickets for sale on the online ticket marketplace; and an offered sale price for each ticket of the plurality of tickets for sale.
6. The method of claim 1, wherein the set of ticket information comprises at least one of (i) a ticket section identifier or (ii) a ticket seat identifier, for each ticket of a plurality of tickets for sale on the online ticket marketplace.
7. The method of claim 1, wherein the input from the client device comprises at least one of (i) a ticket preference or (ii) a price preference.
8. The method of claim 1, wherein the subset of ticket information for the event provides ticket pricing information as a function of time.
9. The method of claim 1, further comprising: based on the input from the client device, scraping the online ticket marketplace for a second set of ticket information; and based on the input from the client device, storing the second set of ticket information to the historical database.
10. The method of claim 1, wherein at least a portion of the subset of ticket information generated by the server is information not displayed by the online ticket marketplace.
11. The method of claim 1, wherein the subset of ticket information for the event comprises a set of daily ticket history information, wherein the set of daily ticket history information comprises (i) a number of total tickets available and (ii) a set of pricing information.
12. The method of claim 1, wherein the subset of ticket information comprises a number of primary market tickets available and a number of secondary market tickets available.
13. The method of claim 1, wherein the subset of ticket information comprises a count of tickets sorted by price.
14. The method of claim 1, wherein the subset of ticket information for the event is configured to be filtered by a section identifier or a price value.
15. The method of claim 1, further comprising:(c) scraping, by the server, a second online ticket marketplace for a second set of ticket information relating to the event;(d) storing, by the server, the second set of ticket information; generating, by the server, the historical database of ticket information for the event by repeating steps (c) and (d) on a second predetermined interval.
16. A computing system, comprising: a communication interface; a processing unit; a data storage; and program instructions stored in the at least one data storage, wherein the program instructions are executable by the processing unit to carry out operations comprising:(a) scraping, by a server, an online ticket marketplace for a set of ticket information relating to an event;(b) storing, by the server, the set of ticket information; generating, by the server, a historical database of ticket information for the event by repeating steps (a) and (b) on a predetermined interval; based on an input from a client device, generating, by the server, a subset of ticket information for the event from the historical database of ticket information for the event; and displaying, by the server, the subset of ticket information.
17. A method, comprising: accessing, by a server, an event webpage of a website, wherein the website is one of a set of ticket marketplace websites, wherein the event webpage corresponds to an event, and wherein the event webpage comprises a first set of ticket data associated with the event; collecting, by the server, the first set of ticket data at a predetermined interval; storing, by the server, the collected first set of ticket data; generating, by the server, a second set of ticket data based on the stored first set of ticket data; and displaying the second set of ticket data within the event webpage.
18. The method of claim 17, wherein the first set of ticket data comprises: a number of a plurality of tickets listed for sale on the event webpage; a ticket section identifier for each ticket of the plurality of tickets listed for sale; and an offered sale price for each ticket of the plurality of tickets listed for sale.
19. The method of claim 17, wherein displaying the second set of ticket data comprises displaying a representation of a set of pricing ticket information over time.
20. The method of claim 19, wherein the set of pricing information comprises: a number of tickets available per day, and an average ticket price per day.