By design, the triPOS Cloud API and integration is very similar to triPOS PC. Current integrators to triPOS PC will find that they will need to make very few changes to integrate to triPOS Cloud. Below is a list of the differences in the API between triPOS Cloud and triPOS PC.
- Credentials in the Header. In triPOS PC, the credentials can either be sent in the header of every request, or reside in the triPOS.config file. In triPOS Cloud, the credentials are required to be sent in the header of every request.
- HTTPS and HMAC Signing. In triPOS PC, the use of HTTPS is optional. In triPOS Cloud, the use of HTTPS is required, and consequently, signing requests with an HMAC signature is no longer necessary.
- Transaction Configuration. In triPOS PC, several transaction configuration values are set in the triPOS.config file. In triPOS Cloud, these values are sent in through the API. For example, if an ISV supports debit and wants to enable cashback, the debit and cashback values should be sent directly in the sale request.
- Configuration Endpoints. The configuration endpoints are different for triPOS Cloud. The application, host, transaction, server, and serial lane endpoints are not necessary. Additionally, when adding an IP lane, triPOS Cloud requires an ISV to send in the activation code shown on the PIN pad.
- Strict XML Serialization. In triPOS PC, the ISV has the choice of whether to use strict XML serialization. By default, triPOS Cloud uses strict XML serialization. For example, in triPOS Cloud, ISVs will need to use XML arrays instead of comma delimited lists when sending in an array of values.
- Request ID. In triPOS PC, sending a tp-request-id header, the unique ID for each request, is optional. In triPOS Cloud, the tp-request-id header is required.
- Response Logs. In triPOS PC, a header value named tp-return-logs could be sent to get return trace logs on the response. In triPOS Cloud, trace logs are not available and this header is ignored.