Ticket listing triggered by URL links
A ticket purchase application is installed in a communication device to facilitate event ticket purchase. An operating system of the communication device recognizes a type of Uniform Resource Locator (URL) that indicates an entertaining or sporting event. The URL includes a unique code associated with a specific event. The operating system of the communication device may detect user interactions that trigger the URL. When the URL is triggered, the ticket purchase application may be started and the unique code in the URL may be parsed and forwarded to the ticket purchase application. The ticket purchase application uses the unique code to identify the event and searches for tickets associated with the event. The ticket purchase application may list available tickets of the event in an order based on the user's preference. Accordingly, a user may quickly find and purchase a desired ticket by clicking on an URL.
1. A method, comprising:
providing registration information to an operating system of a computing device when a ticket purchasing application is installed on the computing device;
automatically launching the ticket purchasing application by the operating system of the computing device when a particular type of a Uniform Resource Locator, identified by the registration information, is selected by a browser application installed in the computing device, wherein the particular type of a Uniform Resource Locator includes an event identifier that corresponds to a ticketed entertaining or sporting event;
receiving, from the operating system, the event identifier;
querying a ticket exchange service provider for one or more tickets associated with the event identifier; and
providing results of the query to the operating system of the computing device.
2. The method of claim 1 , wherein querying the ticket exchange service provider comprises querying one or more databases associated with the ticket exchange service provider using the event identifier.
3. The method of claim 1 , wherein a result of the querying is displayed in an order that is based, at least in part, on user preference information identified by the application.
4. The method of claim 3 , wherein the user preference information is determined, based at least in part, on a user interaction with the application.
5. The method of claim 3 , wherein the user preference information is based, at least in part, on a purchase history.
6. The method of claim 3 , wherein the user preference information is based, at least in part, on a browsing history associated with one or more received searches for ticketed events.
7. The method of claim 1 , wherein the application is a ticket purchase application.
8. A method, comprising:
providing a registration information to an operating system of a computing device when a ticket purchasing application is installed on the computing device;
automatically launching the ticket purchasing application by the operating system of the computing device when a particular type of a Uniform Resource Locator, identified by the registration information, is selected by a browser application installed in the computing device, wherein the particular type of a Uniform Resource Locator includes a unique identifier that corresponds to a particular result of a received query associated with a ticketed entertaining or sporting event;
receiving, from the operating system of the computing device, the unique identifier;
using the unique identifier to query a database for the particular result associated with the unique identifier; and
providing the particular result to the operating system of the computing device.
9. The method of claim 8 , wherein the application is a ticket purchase application.
10. The method of claim 8 , wherein the unique identifier is used to identify a ticketed event.
11. The method of claim 8 , wherein the database is associated with a ticket exchange service provider.
12. The method of claim 8 , wherein the particular result is identified based, at least in part, on stored preference information.
13. The method of claim 12 , wherein the stored preference information is based, at least in part, on a received interaction with the application.
14. The method of claim 12 , wherein the stored preference information is based, at least in part, on a browsing history associated with one or more received searches for similar particular results.
15. A method, comprising:
receiving registration information from a ticket purchasing application installed on a computing device;
automatically launching the ticket purchasing application by the computing device when a first Uniform Resource Locator, displayed on a user interface of the computing device, is selected by a browser application installed in the computing device;
determining whether the first Uniform Resource Locator is a particular type of Uniform Resource Locator identified by the registration information of the application, wherein the particular type of Uniform Resource Locator includes an event identifier that corresponds to a ticketed entertaining or sporting event;
when it is determined that the first Uniform Resource Locator is the particular type of Uniform Resource Locator identified by the registration information of the application:
parsing the first Uniform Resource Locator to identify query information contained in the first Uniform Resource Locator;
automatically launching the application; and
providing the query information to the application.
16. The method of claim 15 , wherein the application is a ticket purchase application.
17. The method of claim 15 , wherein the query information is a unique identifier associated with a one or more query results.
18. The method of claim 17 , wherein the one or more query results include one or more results to ticketed events.
19. The method of claim 18 , wherein the one or more results to ticketed events are displayed using a display preference information.
20. The method of claim 19 , wherein the display preference information is based, at least in part, on received application interaction data.