API v.1
1. Introduction
Note: API v.1 is one of our legacy APIs and we no longer support this version for new integrations.
Whilst we will not be adding new features into this version, we will maintain this API for the foreseeable future to support legacy integrations. We do not currently have any plans to switch off this API but will notify known users if this situation changes.
New integrations should use the current version of our API.
The Spektrix Api v1.0 is designed to allow 3rd party web applications to retrieve an events feed from the Spektrix system. The feed provides basic event information and the dates and times of the instances of each event. The information is thus quite ‘high level’ and does not include a lot of the intricate details that the Spektrix system itself deals with - the aim at v1.0 was to allow 3rd party websites to be able to filter and list events to provide event calendar and event list functionality.
To proceed to selling the event the 3rd party website should pass the customer into the Iframe booking path. We recommend this transition occurs at the chooseseats.aspx Iframe to create a smooth booking experience with the least number of steps. Details of how to integrate the Iframes can be found here.
The Spektrix API v1.0 supports two protocols, SOAP and REST. The following sections give an overview of the interfaces available on each protocol.
2. System Concepts
Note that the terms event and event instance used in this section refer to internal Spektrix system data, not the data available through the API. For more information on terms used in Spektrix, please refer to our glossary of system concepts
3. Polling
To improve the performance of your website it can be advantageous to poll the Spektrix API and cache the data locally. While this can be an effective way to increase performance polling too frequently can put unnecessary load on the Spektrix servers. To discourage abuse, the Spektrix API caches the data itself. If polling occurs at too high a frequency than the API will simply return the cached record, not the fresh version. If you do poll for data, please do not poll more than once every 30 minutes for data.
4. SOAP Events Interface

The SOAP Events web service has a schema that maps onto the conceptual UML diagram shown in Figure 1. Data are represented as properties of dumb classes and the API functions are represented as methods of interfaces. Please refer to Section 6.1 for a detailed description of the data obtained from the interface.
The service can be accessed at
https://system.spektrix.com/clientname/api/v1/events.svc
and its WSDL can be obtained through
https://system.spektrix.com/clientname/api/v1/events.svc?wsdl
where clientname should be replaced with the appropriate client name, which can be obtained from either the venue or Spektrix support.
4.1. GetByDate
Returns an array of events that have instances between the given dates, or all events if no dates are given. The array of EventTime elements in the events returned will only include instances that occur between the dates given.
| Parameters: | ||
|---|---|---|
| dateFrom | Optional | Inclusive date/time. Only events with instances occurring on or after the value will be returned. |
| dateTo | Optional | Inclusive date/time. Only events with instances occurring on or before the value will be returned. |