SpecialRequests options for ReserveTickets

Hello,

Quick question here,

What are all the options we can use for the SpecialRequests in the Web/Cart/{sessionKey}/Tickets function.

The documentation for the operation says to "See the special requests section", however I do not see where that exists...

The important one I needed was "LeaveSingleSeats", and thankfully I found that answer for that one in the forums somewhere.   So now I am wondering what else there is.

I would like one for the reserve held seats.  If possible I would rather use the special requests rather than alter our T_DEFAULTS to allow those reservations.

Thanks much

... Howard

Parents
  • To answer my own question:...

    I found this list back in the SOAP API Guide documentation.  I will assume that these are the same for the REST call I am using...

    I will paste it here in case someone else that needs it finds this post or for when the reference guide disappears because of the SOAP API sunset...:

    Still not quite sure exactly how the "HoldCode" request (at the bottom of this list) works..  That might be useful for my application..  Is there some further explanation for what that does?

    APPENDIX:  SPECIAL REQUESTS

    Select Tessitura API methods allow for special requests to be passed when reserving seats. The special requests must match the following name value pairs. If they do not match, they will not be sent to the Tessitura system.

    Special requests should be represented in a standard URL parameter format. That is, names are separated from values by ‘=’, and each name-value pair is separated by ‘&’. For example:

    NoStairs=Y&AisleSeat=L

    Name

    Data Type

    Value

    ContiguousSeats

    INTEGER

    0 to Maximum Seats/Request

    WheelChairSeats

    INTEGER

    0 to Maximum Seats/Request

    NoStairs

    CHAR(1)

    'Y','N'

    AisleSeat

    CHAR(1)

    ‘L’,’R’,’A’,’N’

    StartingPrice

    MONEY

    0 to Maximum Price

    EndingPrice

    MONEY

    0 to Maximum Price

    StartingRow

    CHAR(10)

    Row in seat map

    EndingRow

    CHAR(10)

    Row in seat map

    StartingSeat

    CHAR(10)

    Seat in seat map

    EndingSeat

    CHAR(10)

    Seat in seat map

    LeaveSingleSeats

    CHAR(1)

    ‘Y’,’N’

    HoldCode

    INTEGER

    A valid value from T_HC.hc_no

Reply
  • To answer my own question:...

    I found this list back in the SOAP API Guide documentation.  I will assume that these are the same for the REST call I am using...

    I will paste it here in case someone else that needs it finds this post or for when the reference guide disappears because of the SOAP API sunset...:

    Still not quite sure exactly how the "HoldCode" request (at the bottom of this list) works..  That might be useful for my application..  Is there some further explanation for what that does?

    APPENDIX:  SPECIAL REQUESTS

    Select Tessitura API methods allow for special requests to be passed when reserving seats. The special requests must match the following name value pairs. If they do not match, they will not be sent to the Tessitura system.

    Special requests should be represented in a standard URL parameter format. That is, names are separated from values by ‘=’, and each name-value pair is separated by ‘&’. For example:

    NoStairs=Y&AisleSeat=L

    Name

    Data Type

    Value

    ContiguousSeats

    INTEGER

    0 to Maximum Seats/Request

    WheelChairSeats

    INTEGER

    0 to Maximum Seats/Request

    NoStairs

    CHAR(1)

    'Y','N'

    AisleSeat

    CHAR(1)

    ‘L’,’R’,’A’,’N’

    StartingPrice

    MONEY

    0 to Maximum Price

    EndingPrice

    MONEY

    0 to Maximum Price

    StartingRow

    CHAR(10)

    Row in seat map

    EndingRow

    CHAR(10)

    Row in seat map

    StartingSeat

    CHAR(10)

    Seat in seat map

    EndingSeat

    CHAR(10)

    Seat in seat map

    LeaveSingleSeats

    CHAR(1)

    ‘Y’,’N’

    HoldCode

    INTEGER

    A valid value from T_HC.hc_no

Children
No Data