triPOS REST API

<back to all web services

LastTransactionRequest

The following routes are available for this service:
GET/api/v1/lastTransaction/{laneId}Gets a last Financial Transaction Response based on laneIdGets a last Financial Transaction Response based on laneId.See documentation for more information.
LaneRequest Parameters:
NameParameterData TypeRequiredDescription
CardHolderPresentCodeformCardHolderPresentCode?NoDefines whether the cardholder is present at the transaction. This value is optional, but recommended to be set. If this value is not set in the request, it will be automatically set based on the market code.

Allowable Values

  • Default
  • Unknown
  • Present
  • NotPresent
  • MailOrder
  • PhoneOrder
  • StandingAuth
  • ECommerce
ClerkNumberformstringNoAn optional clerk number for reference.
LaneIdformintNoSpecifies which lane to use.
ReferenceNumberformstringNoA user defined reference number.
ShiftIdformstringNoAn optional shift id for reference.
TicketNumberformstringNoAn optional ticket number.
LastTransactionResponse Parameters:
NameParameterData TypeRequiredDescription
TypeformstringNoThe type of object held in the result.
StatusMessageformstringNoA message describing the status of the last transaction.

To override the Content-type in your clients, use the HTTP Accept Header, append the .json suffix or ?format=json

To embed the response in a jsonp callback, append ?callback=myCallback

HTTP + JSON

The following are sample HTTP requests and responses. The placeholders shown need to be replaced with actual values.

POST /json/reply/LastTransactionRequest HTTP/1.1 
Host: triposqa.vantiv.com 
Content-Type: application/json
Content-Length: length

{"cardHolderPresentCode":"Default","clerkNumber":"String","laneId":0,"referenceNumber":"String","shiftId":"String","ticketNumber":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"type":"String","statusMessage":"String"}