Api2
Contents
API2 Integration
The RTS API 2 is a rest service allowing 3rd party access to the POS system.
Communcation
Communications with the locations POS server are done using a HTTPS Post of a JSON packet.
Each individual location has an assigned RTN number which is used to route packets.
The DNS for posting data is:
https://<RTN>-api2.formovietickets.com:port/app/api/v2/<EndPoint>
Most RTNs are configured to use port 2235 although this should be configurable as some locations use a different port.
Test Servers
We maintain test servers that process credit cards via different providers.
- Plain Text
- RTN 5, port 2235.
This is a classic server where plain text credit card information is processed.
This is not an 'Out-Of-Scope' process and is seldom used.
- MercuryPay/WorldPay/FIS Hosted Checkout
- RTN 500636, port 2245
This processor required you to redirect users to their page for credit card entries
- Heartland Hosted Checkout
- RTN 321033, port 2255
This processor provides java script 'controls' which allows processing credit cards 'Out-Of-Scope' without the customer leaving your site.
- TSYS Hosted Checkout
- RTN 809261, port 2265
This processor provides java script 'controls' which allows processing credit cards 'Out-Of-Scope' without the customer leaving your site.
Developer ID
Each company must request a developer ID before API calls will function. We provide this free of charge.
Info Packet
Each packet starts with a JSON info object which contains your Developer ID, Company Name, UserID, Password, RTN, and email addresses.
One or more email addresses are required, we use these addresses internally if we need to notify you of API usage issues with your integration.
{
"info": { "userId": "test", "password": "test", "rtn": "5", "developerId": "23b21ecb874c4e318e6ddf85518a54495ae08efa4fb5d792aa28cbfc60bf0f99", "company": "Ready Theatre Systems LLC", "emails": [ "support@rts-solutions.com" ] }
PurchaseInfo Packet
Most requests require a PurchaseInfo object. This is primarily used to detect credit card fraud. If your API call requires this packet it must be initiated by a customer interaction from your APP or website.
"purchaseInfo": { "ip": "1.1.1.1", "deviceId": "", "trackingId": "d9876c6a-fda2-427e-aa07-d177d560b824" }