API System Concepts

  • Regional Organization  This is the parent entity that owns or administers the ticketing services.  The regional organization is used to host multiple venues or groups that sell tickets.  System users and customer records are stored at this level.
  • Corp Level Organization  This is the entity that represents the individual venues or groups that sell tickets. It provides for management of payment methods, buyer types (e.g. General Public, Member), accounting information, and several other high level details.
  • Buyer Type  This is our method of segmenting sales for the purposes of allowing members/groups access to items not available to the general public. You will notice a link to Events and Event prices, this allows flexibility for events to be available/unavailable on certain buyer types and different price structures for different buyer types.
  • Event Level Organization  This is the entity under which Events will be set up. It is possible to have more than one event level organization to allow for segmentation.
  • Venue  This is the location of the event.  These may be set up at both the corp level organization and the event level organization.
  • Event  This represents information about the event like name, date and time, duration, description, etc.
  • Tier  A tier is the first level of how Agile segments out inventory (e.g. Admission, VIP).  You might have 200 tickets available to the general public at one price and 50 tickets available near the front of the venue for a higher price. It is also possible to place quantities of inventory within a tier into hold groups. For Example out of the 200 available to general public you might want to place 20 of the seats into a hold group for problem resolution.
  • Event Price  This is an actual ticket that is able to be purchased by a customer. It contains fields like ticket type (e.g. Adult, Child), price amount, promotion codes, min/max per order, and many other details.  Each event price is tied to a specific buyer type.  This allows for different pricing structures for different buyer types.
  • Orders  Each time a customer makes an order they create an order in the Agile database and an initial transaction. Any maintenance (e.g. ticket cancel, ticket printing, price changing) will create a new transaction associated with the order.
  • Transaction  This represents groups of activity against an order. It contains information such as the user doing the activity and the location/terminal where the activity is occurring, and many other details.
  • Order Log  For each ticket that is purchased in the Agile system there is an orderlog which will have details such as delivery method (e.g. Will Call , Mail, Print At Home), barcode, purchase price, and other details
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request