Website Integration Options

Agile Ticketing provides several options for integrating the ticket purchase process into your website.  Check out the document below to see further details about these options.

 

Web Integration Options 

 

WebSales Feed API

Agile Ticketing’s WebSales Feed allows third party developers to easily pull information from our database into their websites. This level of integration is used most often since it requires less time and coding than the deeper API integration. The feed is available for request as JSON or as XML and there are several query parameters that allow for manipulation of what is returned. It can also be requested as a file download which can be periodically digested into an external site.

 

Example WebSales Feed URLs
https://prod1.agileticketing.net/websales/feed.ashx?guid={GUID}&showslist=true&format=xml&

https://prod1.agileticketing.net/websales/feed.ashx?guid={GUID}&showslist=true&format=json&

 

Important Information About WebSales Feed Usage
The Agile Ticketing WebSales Feed has usage limits to avoid overuse degrading the overall user experience. The limits are primarily here to protect the system from over use by external systems, not to restrict you as a user and can be evaluated on an as needed basis.

If you are building a web page using the Agile Ticketing WebSales Feed, we recommend that you do all GET requests on the server side, and cache the results for a short period of time. If you get substantial traffic on your site you would not want to call the WebSales Feed each time you get a page hit, since this may cause you to hit the request limit faster than expected. In general, whenever you can cache data like this you should do so. The WebSales Feed data on the Agile server is only updated every 10 minutes so getting the data more often than that won’t give you much of an advantage.

Remember that the internet can be unreliable. Your application should not assume it will get an answer. By using proper caching of the WebSales Feed data on your server you will be able to provide a consistent user experience even if there are internet issues between your server and Agile.

Refer to the documentation below for more information about how to use Agile’s WebSales Feed.

WebSales Feed Details

Getting a GUID
Parameters
Return Values
Return Values (showslist=true)
Login/Cart Widget
iframe Integration


Advanced API

Agile Ticketing’s API allows third party developers to leverage our ticketing infrastructure to build innovation new applications.  The API allows communication via JSON or XML.  The communication method is determined by the URL used to reference the API.

Example Web Service URLs

JSON URL:  https://prod1.agileticketing.net/api/sales.svc/json/{MethodName}
XML URL:  https://prod1.agileticketing.net/api/sales.svc/xml/{MethodName}

Refer to the documentation below for more information about each of the supported API methods.

 

Sales Service (Event Sales Only)

Show List
Event List
Event Get
Event Get Description
Event Get ID From External ID
Event Sales Status
Event List Prices
Venue List
Venue Get
Buyer Type List
Inventory Group List
Org Control Get
Membership List Access
Member Restriction List

Authenticate Email
Authenticate Member
Customer Add
Customer Update
Customer Search
Customer List Streaming
Customer Get Streaming
Customer Redeem Streaming
Customer List Event History
Customer List EDelivery
Web User Add
Web User Update
Order Add Items
Order Delete Items
Order Status
Order Update
Order Transfer
Order Cancel
Order Void

Legacy Methods
Order Start
Tickets Add
 

Gate Control Service

Authenticate User
List Orgs
List Batches
Validate Barcode
Download Valid Barcodes
List Messages
Batch Stats
 

Additional Information

Error Codes
System Concepts
Sales API Guidelines