API Documentation

From Rts
Revision as of 22:20, 12 September 2020 by CortlandH (talk | contribs)
Jump to: navigation, search

Contents

Version Change History

Date Change Notes Version
12/28/08 Added Error Listing 0.2
06/16/09 Added Retrieve Seating Chart Section 1.0
06/17/09 Added PHP sample code 1.01
03/15/10 Added the CustomerInfo and EmailAddress tags. Used to look-up transactions at the POS. 1.02
04/13/10 Added Gift Balance functions (requires server version 7.0.7564+).

Added gift number to purchase request, which allows adding money to an existing gift card (requires server version 7.0.7564+).

1.03
11/22/10 General document clean-up.

Corrected 'GiftInfo' to be 'GiftInformation'.
Added information for concession prices XML and concession sales.
Added 'SalesTaxCheck' information.
Moved all references regarding encryption to summary pages at back of documentation.
Updated PHP sample code to use TLS for the connection protocol.

1.04
11/30/10 Added test server information, credit card information, gift card information, etc

Updated PHP sample code to contain additional sample packets

1.05
12/13/10 Added sample of purchase ticket response

Updated sample response for GiftInformation, showing Registered Card information

1.06
06/11/13 Added multiple <Payment> sample

Added GroupID for Reserved Seating – Seat Chart
Added Registering a mag card
Added earning loyalty points for purchases
Added CardCredits to GiftInformation sample response

1.07
01/07/2014 Corrected an error in the Fees section regarding <TicketFee> 1.08
01/15/2015 emoved sample code (too many people using for production environments)

Switched from DIGEST to BASIC authentication
Added new error codes
Removed HTTP + Encryption section (no longer relevant)
Added CheckSoldOut request – shows Sold /Remaining / SoldOut levels for a performance

1.09
03/20/2015 Removed obsolete Seating Chart sample request 1.10
06/03/2015 Added WorldPay HostedCheckout sample requests and responses

Added 3rd party credit card processing sample request
Added listing of bit field settings used for films and shows
Added new error numbers / messages
Updated existing error numbers / messages

1.11
10/24/2016 Added CheckRedeem request sample

Added GetSeatLayouts request sample
Added GetSeatPlanForPerf request sample
Added CheckSeatPicks request sample
Added VerifyTransaction request sample
Added ReverseTransaction request sample
Added Refund request sample
Updated BUY request to include <ThirdPartyID> node information
Simplified table of contents

1.12
02/08/2017 Added Bit Field values for various new amenities 1.13
05/30/2017 Fixed documentation error with the CHECKSEATPICKS response 1.14
10/19/2017 Fixed typo in ‘CHECKSEATPICKS’ sample request

Added GridRef to ‘GETSEATPLANFORPERF’ response

1.15
02/02/2018 Added note regarding GZIP compression now being required for schedule request 1.16
07/24/2018 Updated test credit card information

Added Bit Field values for various new amenities

1.17
08/13/2018 Added TransactionDetails request sample

Added Redeem request sample
Updated Refund request to include PartialRefund support

1.18
09/26/2019 Added <SOGen> node to schedule data to indicate SoldOutGeneral state
Updated verbiage on <SO> and
  • node descriptions
    Added gift card PIN node to BUY request
    Added 3rd party gift card support
    Added custom seat pricing data to GETSEATPLANFORPERF call
    Added note regarding send confirmation emails on purchase via API
    Updated existing error numbers / messagess
    		• 1.19
    11/25/2019 Updated seat type nodes to support new types

    Added support for 3rd party gift cards into the GIFTINFORMATON call
    Added a call for GIFTINFORMATIONWITHPIN to support PIN requiring card types

    		1.20
    01/31/2020 Added Heartland HostedCheckout test card information

    Added Heartland HostedCheckout sample requests and responses
    Added Heartland HostedCheckout error messages

    		1.21
    05/04/2020 Updated seat status nodes to support Buffer seat status 1.22


    Introduction

    RTS Ticketing has created an open interface to accommodate third party access to our sales engine. In order to allow access, we have created an HTTPS server that accepts XML packets.

    Credit card payments are processed either through the POS locations’ credit card processing account, or through your own processing account. So a separate shopping cart or credit card processing account is not needed, but you have the option of building your own.

    Purchased tickets can be redeemed at the locations POS at for actual tickets. These tickets can be redeemed using any of three methods:

    1. The credit card that was used to purchase the tickets
    2. The receipt number assigned to the purchase
    3. The bar code that is provided by the purchase response packet.


    Note: Some locations do not have bar code readers or the bar code may be illegible when printed on a low-quality printer. It is strongly suggested that the confirmation number is also printed with the bar code.

    Communication

    Communications with the locations POS server are done using a HTTPS Post of an XML packet. Basic authentication is performed for each Post.

    The URL for posting data is:
    https://<Theatre RTN Number>.formovietickets.com:<port>/Data.ASP

    Note: The listening port is 2235 (not the default web server port 80)

    Test Server Information

    It is a good idea to develop your application against a test server, and not against a live theatre server. Below is the information for the RTS Test Servers:

    !! NOTE: These are not web pages, they cannot be viewed in a browser !!

    WorldPay Non-E2E Server (also known as Mercury Classic Server):
    The endpoint URL is: https://5.formovietickets.com:2235/Data.ASP

    WorldPay E2E Server (also known as Mercury EMV Server):
    The endpoint URL is: https://5.formovietickets.com:2245/Data.ASP

    Heartland Secure Server:
    The endpoint URL is: https://5.formovietickets.com:2255/Data.ASP

    The credentials for these servers are:

    Schedule and Selling Username: test
    Schedule and Selling Password: test

    Test Card Information

    !! NOTE: The <ChargeAmount> for the test WorldPay cards cannot exceed $10 !!

    The test credit card information for the WorldPay Non-E2E server is:

    Number 5499-9901-2345-6781
    Expiration Any future month and year (mmyy format)
    AVS Street 150 Mercury Village
    AVS Postal 81301
    CVV 5499-9901-2345-6781
    Customer Name Any name

    The test credit card information for the WorldPay E2E server is:

    Number 4003-0001-2345-6781
    Expiration Any future month and year (mmyy format)
    AVS Street 150 Mercury Village
    AVS Postal 81301
    CVV 5499-9901-2345-6781
    Customer Name Any name

    The test credit card information for the Heartland Secure server is:

    Number 4640-6977-8499-8
    Expiration 12 / 2025
    AVS Street 6860 Dallas Pkwy
    AVS Postal 75024
    CVV 5499-9901-2345-6781
    Customer Name Any name

    To obtain a test gift card number, purchase a new gift card, and then use the returned number as your future test gift card number. See Gift Card / Loyalty Card Information for details on purchasing new gift cards.

    Performance Schedule

    !! NOTE: GZIP Compression is required when requesting schedule data !!

    !! NOTE: Sending in <ShowAvalTickets> and <ShowSales> values that do not match the settings on the locations configured schedule API account will result in a 401 – Unauthorized error !!

    Performance Schedule - Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>ShowTimeXml</Command>
    <ShowAvalTickets>1</ShowAvalTickets>
    <ShowSales>1</ShowSales>
    <ShowSaleLinks>1</ShowSaleLinks>
</Request>

    Performance Schedule - Sample Response Packet

    <Response>
    <ShowSchedule>
        <FileVersion>1.1</FileVersion>
        <RtsVersion>7.0.7238.0</RtsVersion>
        <LinkPrefix> https://www.readyticket.net/webticket/webticket2.aspWCI=BuyTicket&WCI=
</LinkPrefix>
        <Tickets>
            <Ticket>
                <Code>1</Code>
                <Name>Adult</Name>
                <Price>7.5</Price>
                <Tax>.5</Tax>
            </Ticket>
            <Ticket>
                <Code>2</Code>
                <Name>Child</Name>
                <Price>7</Price>
                <Tax>.43</Tax>
            </Ticket>
        </Tickets>
        <Films>
            <Film>
                <Title>+21 STRANGE TITLE</Title>
                <TitleShort>+21 STRANGE TITLE</TitleShort>
                <Length>120</Length>
                <Rating>NC17</Rating>
                <WebSite>http://www.rts-solutions.com</WebSite>
                <FilmCode>+24230</FilmCode>
                <MtFilmCode></MtFilmCode>
                <Shows>
                    <Show>
                        <DT>200811261235</DT>
                        <Aud>1</Aud>
                        <ID>+24230|200811261235|1</ID>
                        <SaleLink>%2B21+STRANGE+TITLE,112620081235,1,5,NC17</SaleLink>
                        <RE>225</RE>
                        <Sold>22</Sold>
                        <SO>0</SO>
                        <LI>0</LI>
                        <TIs>
                            <TI>
                                <C>1|1</C>
                            </TI>
                            <TI>
                                <C>1|2</C>
                            </TI>
                        </TIs>
                    </Show>
                </Shows>
            </Film>
        </Films>
    </ShowSchedule>
</Response>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None Char Yes ShowTimeXml
    ShowAvalTickets None Integer No Not 1 = Do not return available tickets (default)

    1 = Return available tickets

    ShowSales None Integer No Not 1 = Do not return sales (default)

    1 = Return sales

    Node Child Node Type Required Description <ShowSchedule>
    FileVersion None String Yes 1.1
    RtsVersion None String Yes Version of the POS
    LinkPrefix None String Yes Used to construct a direct ticketing link for a performance
    Tickets Ticket Sub Node Maybe Lists available tickets
    Films Film Sub Node Yes Lists films scheduled
    Node Child Node Type Required Description <Ticket>
    Code None String Yes Ticket code used in purchase transactions
    Name None String Yes Ticket name as it should be displayed on the Internet
    Price None Decimal Yes Total ticket price
    Tax None Decimal Maybe Any tax included in the ticket price
    Node Child Node Type Required Description <Film>
    Title None String Yes Film title name
    Length None String Yes Film length (minutes)
    WebSite None String Maybe URL associated with the film in the POS
    FilmCode None String Maybe RTS Film Code setup in the POS
    Shows Show Sub Node Yes List of available shows for a film
    Node Child Node Type Required Description <Show>
    DT None String Yes Showing time (yyyyMMddhhmm)
    Aud None String Yes Auditorium name
    ID None String Yes Performance ID, used in purchase transactions
    Link None String Maybe URL to purchase tickets page. The <LinkPrefix> is inserted before this tag when creating the complete URL
    RE None Integer Maybe Number of seats remaining in the auditorium
    Sold None Integer Maybe Number of seats sold in the auditorium
    SO None Integer Maybe 1 if show is sold out (internet) state
    SOGen None Integer Maybe 1 if show is sold out (general) state
    LI None Integer Maybe 1 if show is in low seats state
    TIs TI Sub Node Maybe List of tickets available for this show

    Selling - Fees and Adjustments

    The Open Interface API currently allows for 2 different types of Fees, and an Adjustment.

    The <TicketFee> item is a single charge added to the transaction.

    The <TransactionFee> item is a single charge added to the transaction.

    The <Adjust> item is an adjustment used to modify the charge amount. If you sell 3 tickets with -$1 in this item, it will deduct $1 from your transaction amount. This amount can be positive or negative, depending on how you wish to adjust the transaction.

    All three of these items are placed inside the <Fees> tags inside the purchase packet, see page 13 for a sample packet. These items can be used in any purchase packet: tickets, items, gift cards, etc.

    Gift Card / Loyalty Card Information

    Gift Card / Loyalty Card - Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>GiftInformation</Command>
    <Data>
        <Packet>
            <GiftCards>
                <GiftCard>1234123412341234</GiftCard>
            </GiftCards>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Show>
    Version None Char Yes 1
    Command None String Yes GiftInformation
    Data Packet Sub Node Yes
    Packet GiftCards Sub Node Yes
    GiftCards GiftCard Sub Node Yes
    GiftCard None String Yes Gift card number

    Gift Card / Loyalty Card - Sample Response Packet – Non-Registered Card

    <Response>
    <Version>1</Version>
    <Code>-1</Code>
    <Packet>
        <GiftCard>
            <GiftNumber>1234123412341234</GiftNumber>
            <DebitRemain>1061.16</DebitRemain>
            <Registered>0</Registered>
        </GiftCard>
    </Packet>
</Response>

    Gift Card / Loyalty Card (With PIN) - Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>GiftInformationWithPIN</Command>
    <Data>
        <Packet>
            <GiftCards>
                <GiftCard>
                    <CardNumber>1234123412341234</CardNumber>
                    <CardPIN>1234</CardPIN>
                </GiftCard>
            </GiftCards>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes GiftInformation
    Data Packet Sub Node Yes
    Packet GiftCards Sub Node Yes
    GiftCards GiftCard Sub Node Yes
    GiftCard None String Yes One <GiftCard> node for each card in request
    CardNumber None String Yes Gift card number
    CardPIN None String Yes Gift card PIN

    Gift Card / Loyalty Card (With PIN) - Sample Response Packet – Non-Registered Card

    <Response>
    <Version>1</Version>
    <Code>-1</Code>
    <Packet>
        <GiftCard>
            <GiftNumber>1234123412341234</GiftNumber>
            <DebitRemain>1061.16</DebitRemain>
            <Registered>0</Registered>
        </GiftCard>
    </Packet>
</Response>

    Gift Card / Loyalty Card - Sample Response Packet – Registered Card

    !! NOTE: RTS mag cards are the only type that will return registration data !!

    <Response>
    <Version>1</Version>
    <Code>-1</Code>
    <Packet>
        <GiftCard>
            <GiftNumber>2012700000745808</GiftNumber>
            <DebitRemain>1061.16</DebitRemain>
            <Registered>1</Registered>
            <RegisteredInfo>
                <FirstName>JOHN</FirstName>
                <LastName>DOE</LastName>
                <Address1>4 DOE ROAD</Address1>
                <Address2/>
                <City>DOEVILLE</City>
                <State>DO</State>
                <Postal>11111</Postal>
            </RegisteredInfo>
            <CardCredits>
                <TicketCredit>
                    <Expiration>None</Expiration>
                    <StartDate>None</StartDate>
                    <Amount>1</Amount>
                    <TitleRestriction/>
                    <TicketRestriction/>
                </TicketCredit>
                <TicketCredit>
                    <Expiration>20130405000000</Expiration>
                    <StartDate>20130405000000</StartDate>
                    <Amount>1</Amount>
                    <TitleRestriction>WORLD WAR Z</TitleRestriction>
                    <TicketRestriction/>
                </TicketCredit>
                <ItemCredit>
                    <Expiration>None</Expiration>
                    <StartDate>20130426000000</StartDate>
                    <Amount>1</Amount>
                    <Item>SM POPCORN</Item>
                </ItemCredit>
            </CardCredits>
        </GiftCard>
    </Packet>
</Response>
    Node Child Node Type Required Description <Response>
    Version None Char Yes 1
    Code None Integer Yes -1
    Packet GiftCard Sub Node Yes
    GiftCard RegisteredInfo Sub Node Yes
    GiftCard CardCredits Sub Node Yes
    GiftNumber None String Yes Gift card number
    DebitRemain None Decimal Yes Gift card remaining balance
    Registered None Integer Yes 0 = not registered, 1 = registered
    Node Child Node Type Required Description <RegisteredInfo>
    FirstName None String Yes Customer first name
    LastName None String Yes Customer last name
    Address1 None String Yes Customer street address 1
    Address2 None String Yes Customer street address 2
    City None String Yes Customer city
    State None String Yes Customer state
    Postal None String Yes Customer postal code
    Node Child Node Type Required Description <CardCredits>
    TicketCredit None Sub Node No
    ItemCredit None Sub Node No
    Node Child Node Type Required Description <TicketCredit>
    Expiration None String Yes None = No expiration date, or date of expiration (yyyyMMddhhmmss)
    StartDate None String Yes None = No start date, or date ticket credit becomes valid (yyyyMMddhhmmss)
    Amount None Integer Yes Amount of tickets available
    TitleRestriction None String Yes Empty node = no restriction, or title of movie this credit is good for
    TicketRestriction None String Yes Empty node = no restriction, or name of ticket this credit is good for
    Node Child Node Type Required Description <ItemCredit>
    Expiration None String Yes None = No expiration date, or date of expiration (yyyyMMddhhmmss)
    StartDate None String Yes None = No start date, or date item credit becomes valid (yyyyMMddhhmmss)
    Amount None Integer Yes Amount of item available
    Item None String Yes Name of item credit is good for

    Gift Certificate Purchasing

    New Gift Card Purchase - Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>Buy</Command>
    <Data>
        <Packet>
            <PurchaseGifts>
                <PurchaseGift>
                    <Amount>25</Amount>
                </PurchaseGift>
            </PurchaseGifts>
            <Payments>
                <Payment>
                    <Type>CreditCard</Type>
                    <Number>5499990123456781</Number>
                    <Expiration>0513</Expiration>
                    <AvsStreet>4 Main St</AvsStreet>
                    <AvsPostal>30329</AvsPostal>
                    <CID>123</CID>
                    <NameOnCard>John Doe</NameOnCard>
                    <ChargeAmount>7.5</ChargeAmount>
                </Payment>
            </Payments>
        </Packet>
    </Data>
</Request>

    Add Money to Existing Gift Card Purchase - Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>Buy</Command>
    <Data>
        <Packet>
            <PurchaseGifts>
                <PurchaseGift>
                    <GiftCard>1234-1234-1234-1234</GiftCard>
                    <Amount>25</Amount>
                </PurchaseGift>
            </PurchaseGifts>
            <Payments>
                <Payment>
                    <Type>CreditCard</Type>
                    <Number>5499990123456781</Number>
                    <Expiration>0513</Expiration>
                    <AvsStreet>4 Main St</AvsStreet>
                    <AvsPostal>30329</AvsPostal>
                    <CID>123</CID>
                    <NameOnCard>John Doe</NameOnCard>
                    <ChargeAmount>7.5</ChargeAmount>
                </Payment>
            </Payments>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <PurchaseGifts>
    PurchaseGifts PurchaseGift Sub Node No Contains one or more gift card purchases
    Amount None Decimal Yes Amount to add to the gift card
    GiftCard None String No If specified, amount will be added to the gift card. If not specified, a new number will be generated and the amount added to the new number

    Gift Card Purchase - Sample Response Packet

    <Response>
    <Version>1</Version>
    <Code>-1</Code>
    <Packet>
        <Response>
            <Code>0</Code>
            <ResponseText>OK</ResponseText>
            <TransactionID>1476206</TransactionID>
            <GiftPurchases>
                <GiftPurchase>
                    <GiftNumber>1234-1234-1234-1234</GiftNumber>
                    <Amount>1</Amount>
                </GiftPurchase>
            </GiftPurchases>
        </Response>
    </Packet>
</Response>

    Loyalty Card Information

    Registering a Loyalty Card – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>GIFTINFORMATION</Command>
    <Data>
        <RegisterCards>
            <RegisterCard>
                <CardNumber>12345</CardNumber>
                <FirstName>Jon</FirstName>
                <LastName>Doe</LastName>
                <Address1>Address Line 1</Address1>
                <Address2>Address Line 2</Address2>
                <City>The City</City>
                <State>The State</State>
                <Postal>Postal Code</Postal>
                <RegisteredID>Reg ID</RegisteredID>
                <Email>Support@rts-solutions.com</Email>
                <DOB>19710323</DOB>
                <DoNotEmail>1</DoNotEmail>
            </RegisterCard>
        </RegisterCards>
    </Data>
</Request>

    You can register multiple cards by passing in additional <RegisterCard> nodes.

    Node Child Node Type Required Description <Request>
    Version None integer Yes 1
    Command None String Yes GIFTINFORMATION
    Data RegisterCards Sub Node Yes
    RegisterCards RegisterCard Sub Node Yes
    CardNumber None String Yes Card number to register
    FirstName None String Yes Customer first name
    LastName None String Yes Customer last name
    Address1 None String Yes Customer street address 1
    Address2 None String Yes Customer street address 2
    City None String Yes Customer city
    State None String Yes Customer state
    Postal None String Yes Customer postal code
    RegisteredID None String Yes ????
    Email None String Yes Customer email address
    DOB None String Yes Customer date of birth
    DoNotEmail None String Yes 0 = email, 1 = do not email

    Ticket Purchasing – Check Sold Out

    Checking Performance Sold / Remaining / SoldOut Levels – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>CheckSoldOut</Command>
    <Data>
        <Packet>
            <PerformanceID>013732000045</PerformanceID>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes CheckSoldOut
    PerformanceID None String Yes The PerformanceID for the show to check

    Checking Performance Sold / Remaining / SoldOut Levels – Sample Response Packet

    <Response>
    <Version>1</Version>
    <Sold>3</Sold>
    <IsReserved>0</IsReserved>
    <TotalSeats>500</TotalSeats>
    <SoldOut_General>2</SoldOut_General>
    <SoldOut_Internet>5</SoldOut_Internet>
</Response>
    Node Child Node Type Required Description <Response>
    Version None Char Yes 1
    Sold None Integer No Number of tickets sold to this performance
    IsReserved None Integer No 0 = General Admission, 1 = Reserved
    TotalSeats None Integer No Total number of seats for the show
    SoldOut_General None Integer No General sold out seats remaining level
    SoldOut_Internet None Integer No Internet sold out seats remaining level

    An example of the levels meaning is: 500 seats total, Internet Sold Out happens with 5 seats remaining. Internet Sold Out happens when Sold hits 495.

    If the number of tickets in a transaction is greater than the number seats remaining until Internet Sold Out happens, the transaction will fail.

    Ticket Purchasing – Check Redeem

    This call allows you to see the status of a ticket redemption. If the tickets have not yet been redeemed, the transaction could be refunded or reversed. If the tickets have already been redeemed by the customer, the transaction cannot be altered.

    Checking Ticket Redemption Status – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>CheckRedeem</Command>
    <Data>
        <Packet>
            <PickupNumber>558722177437</PickupNumber>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes CheckRedeem
    PickupNumber None String Yes The PickupNumber from the sale transaction

    Checking Ticket Redemption Status – Sample Response Packet

    <Response>
    <Version>1</Version>
    <Redeemed>1</Redeemed>
</Response>
    Node Child Node Type Required Description <Response>
    Version None Char Yes 1
    Redeemed None Boolean Yes 0 = Not Redeemed, 1 = Redeemed

    Ticket Purchasing – Verify Transaction

    This call allows you to see if a transaction was successfully received and processed. If, for example, you passed in a buy request (that uses the <ThirdPartyID> node) and never received a response from the point-of-sale, this call can be used to see if the transaction was received and processed.

    Found transactions will return the <PickupNumber> associated with the purchase.

    Verify Transaction Status – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>VERIFYTRANSACTION</Command>
    <Data>
        <Packet>
            <ThirdPartyID>63a96a1c66d44b568b3115aeeadc6b12</ThirdPartyID>
            <TransactionDateTimeUTC>20161024153500</TransactionDateTimeUTC>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes VerifyTransaction
    ThirdPartyID None String Yes Your ID for the sale transaction (must have been passed in with the original sale)
    TransactionDateTimeUTC None String Yes The sale transaction date/time in UTC (format:yyyyMMddhhmmss).

    Verify Transaction Status – Sample Response Packet

    <Response>
    <Version>1</Version>
    <TransactionFound>1</TransactionFound>
    <PickupNumber>728722814391</PickupNumber>
</Response>
    Node Child Node Type Required Description <Response>
    Version None Char Yes 1
    TransactionFound None Boolean Yes 0 = Not Found, 1 = Found
    PickupNumber None String No If transaction found, this will be the pickup number for the customer redemption.

    Ticket Purchasing – Transaction Details

    This call lets you retrieve the details of a previous transaction by the PickupNumber associated with the purchase.

    Transaction Details – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>TRANSACTIONDETAILS</Command>
    <Data>
        <Packet>
            <PickupNumber>249728765499</PickupNumber>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes TransactionDetails
    PickupNumber None String Yes The PickupNumber from the sale transaction

    Transaction Details – Sample Response Packet

    <Response>
    <Version>1</Version>
    <TransactionFound>1</TransactionFound>
    <Performances>
        <Performance>
            <Title>ALIEN: COVENANT</Title>
            <DateTime>052920182115</DateTime>
            <Auditorium>2</Auditorium>
            <Tickets>
                <Ticket>
                    <Status>Redeemed - Online</Status>
                    <PickupDateTime>052920181119</PickupDateTime>
                    <Type>senior</Type>
                    <IsReserved>1</IsReserved>
                    <Section>Ruby</Section>
                    <RowDesc>H</RowDesc>
                    <ColDesc>15</ColDesc>
                </Ticket>
            </Tickets>
        </Performance>
    </Performances>
</Response>
    Node Child Node Type Required Description <Response>
    Version None Char Yes 1
    TransactionFound None Boolean Yes 0 = Not Found, 1 = Found
    Performances Performance Sub Node No If transaction found, this will contain the Performance(s) in the transaction.
    Node Child Node Type Required Description <Performances>
    Performance None Sub Node No If transaction found, there will be 1 or more Performance nodes,depending on the transaction contents
    Node Child Node Type Required Description <Performance>
    Title None String Yes The title for this performance
    DateTime None String Yes Performance start time (MMddyyyyhhmm)
    Auditorium None String Yes The auditorium this performance is in
    Tickets Ticket Sub Node Yes The tickets for this performance
    Node Child Node Type Required Description <Tickets>
    Ticket None Sub Node No If transaction found, there will be 1 or more Performance nodes, depending on the transaction contents
    Node Child Node Type Required Description <Ticket>
    Status None String Yes The current status of the ticket pickup:
    Valid - Ticket is available for redemption
    Expired - Ticket has expired
    Refunded - Transaction was refunded via the API
    Reversed - Transaction was reversed via the API
    Redeemed - Online - Ticket was picked up via the API
    Redeemed - Printed - Ticket was picked up in theatre
    PickupDateTime None String Yes Will be present if the ticket is not "Valid" or "Expired" (MMddyyyyhhmm)
    PickupLocation None String Yes Will be present if the ticket was picked up in theatre
    PickupUser None String Yes Will be present if the ticket was picked up in theatre
    Type None String Yes The type of ticket purchased
    IsReserved None Boolean Yes 0 = Not reserved, 1 = Reserved
    Section None String Yes Will be present if the ticket is reserved, indicates the section name the reserved seat is in
    RowDesc None String Yes Will be present if the ticket is reserved, indicates the Row description
    ColDesc None String Yes Will be present if the ticket is reserved, indicates the Column (or Seat) description

    Ticket Purchasing – Redeem Tickets

    This call lets you tell the POS system that you have redeemed tickets via a 3rd party app.

    Redeem – Sample Request Packet

    <Request>
    <Version>1</Version>
    <Command>RDEEM</Command>
    <Data>
        <Packet>
            <PickupNumber>249728765499</PickupNumber>
        </Packet>
    </Data>
</Request>
    Node Child Node Type Required Description <Request>
    Version None Char Yes 1
    Command None String Yes TransactionDetails
    PickupNumber None String Yes The PickupNumber from the sale transaction

    Ticket Purchasing – Refunds

    Ticket Purchasing – Reverse Transaction

    WorldPay E2E - Credit Card Payment Overview

    Credit Card Payments (WorldPay E2E)

    Heartland Secure - Credit Card Payment Overview

    Ticket Purchasing (3rd Party Credit Card Processing)

    Ticket Purchasing – General Admission

    Seating Charts

    Reserved Seating – Check Seat Picks

    Holding and Releasing Seats

    Ticket Purchasing – Reserved Seating

    Concession Prices and Sales

    Error Codes

    Reserved Seating Codes

    Film and Show Bit Field Values

    Retrieved from "https://wiki.readyticket.net/mw/index.php?title=API_Documentation&oldid=5527"