triPOS REST API

<back to all web services

ScrollingDisplayRequest

The following routes are available for this service:
POST/api/v1/scrollingDisplayDisplays an item on an area of the PIN pad screen that scrolls as items are added.Use the scrolling display endpoint to repeatedly add items to a scroll area of the PIN pad screen while displaying the subtotal, tax, and total of the transaction. This endpoint returns an HTTP status code of 200 if the text was successfully displayed on the PIN pad. See scrolling display documentation fore more information.
ScrollingDisplayRequest Parameters:
NameParameterData TypeRequiredDescription
LaneIdbodyintNoThe lane ID.
LineItembodystringNoThe new text line to be added in the scrolling area of the PIN pad screen. It typically includes a description and the price of an individual item (i.e. Cookies... $3.99).
SubtotalbodystringNoThe new subtotal of all the scanned items including the new line item.
TaxbodystringNoThe tax value of the new subtotal.
TotalbodystringNoThe value of the new subtotal and tax.
ApiResponse Parameters:
NameParameterData TypeRequiredDescription
ErrorsformList<ApiError>NoA list of errors that occurred.
HasErrorsformboolNoIndicates if there are errors.
LinksformIEnumerable<ApiLink>NoA list of resource links
LogsformList<string>NoA list of log entries detailing what happened during the request. Ideally only used during development or troubleshooting as this can be quite verbose.
TypeformstringNoThe type of object held in the result.
WarningsformList<ApiWarning>NoA list of warnings that occurred.
ApiError Parameters:
NameParameterData TypeRequiredDescription
UserMessageformstringNoAn error message targeted at the end user of the integrated business application.
DeveloperMessageformstringNoAn error message targeted at the developer of the integrated business application.
ErrorTypeformstringNoCode associated with the error if it exists.
ExceptionMessageformstringNoThe body of the exception message.
ExceptionTypeFullNameformstringNoThe full name of the exception.
ExceptionTypeShortNameformstringNoThe short name of the exception.
ApiLink Parameters:
NameParameterData TypeRequiredDescription
HrefformstringNoA target (a URI)
MethodformstringNoThe HTTP method to access the HREF target
RelationformstringNoThe relation aka. 'rel' (the name of the link)
ApiWarning Parameters:
NameParameterData TypeRequiredDescription
DeveloperMessageformstringNoA warning message targeted at the developer of the integrated business application.
UserMessageformstringNoA warning message targeted at the end user of the integrated business application.

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/ScrollingDisplayRequest HTTP/1.1 
Host: triposqa.vantiv.com 
Content-Type: application/json
Content-Length: length

{"laneId":0,"lineItem":"String","subtotal":"String","tax":"String","total":"String"}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"_errors":[{"userMessage":"String","developerMessage":"String","errorType":"String","exceptionMessage":"String","exceptionTypeFullName":"String","exceptionTypeShortName":"String"}],"_hasErrors":true,"_links":[],"_logs":["String"],"_type":"String","_warnings":[{"developerMessage":"String","userMessage":"String"}]}