Entity Posting API - Ticket Type Add/Update
If the TicketTypeId does not exist, a new Ticket Type record will be created. If it does, it will be updated.
Triggered Updates:
- The name, type and groups for any existing transactions with the TicketTypeId and SiteID will be updated
Standard ShowTimeAnalytics Message Parameters:
- DataSupplierID: Assigned unique identifier for your account
- String
(required) - MessageSequence: Unique sequence number incremented for each message posted
- Long
(required) - CallbackUrl: Dataprovider defined URL that result of processing the message is posted back to
- String
Fields for Ticket Type Entity:
- ID attribute: Unique identifier for Ticket Type
- String
(required)
- SiteID attribute: Unique identifier for site that the ticket type applies to. Only populated if ticket type is local to the site
- String
- Name: Ticket Type name
- String
(required) - Type: Base categorisation for ticket type
- String
- Tags: User defined list of tags they might want to filter on
- String
- Currency: The Currency value that defines the saleprice of the Ticket Type
- ISO-4217 Code
- SalePrice: How much the Ticket Type is sold for
- Integer
- Precision attribute: The number of decimal places in the SalePrice field
- Integer
(required)
- EffectiveFrom: DateTime when the pricing structure for the Ticket Type comes into effect
- ISO-8601 datetime
(required)
PLEASE NOTE: All field and attribute names are case sensitive
Message Structure - XML:
Callback Post Fields:
- DataSupplierID: Unique identifier for your account, same as passed in post message
- MessageSequence: Unique sequence number for message, same as passed in post message
- ID attribute: Unique identifier for Ticket Type, same as passed in post message
- Status: Processing result flag - ok/error
- Error: If the status flag is "error", list of warning messages during processing