triPOS REST API

<back to all web services

BarcodeRequest

The following routes are available for this service:
GET/api/v1/barcode/{laneId}Initiates and retrieves the data from a barcode scan.Use the barcode endpoint to initiate and retrieve the data from a barcode scan of a capable PIN pad. See barcode documentation for more information.
BarcodeRequest Parameters:
NameParameterData TypeRequiredDescription
LaneIdpathintYesThe lane ID.
AimerLightsOnquerystringNoSets the Aimer LED lights on/off.
ImagequerystringNoSets the Image Mode to 1D, 2D, etc.
LightingquerystringNoSets the Lighting Mode to a shorter or longer exposure time.
MessagequerystringNoThe message to be displayed on the PIN pad screen.
ScanLightsOnquerystringNoSets the Scan LED lights on/off.
TimeoutquerystringNoSets the amount of time (in seconds) triPOS should wait to receive the barcode data
UseTriggerquerystringNoSets the option to use the trigger to start a scan.
BarcodeResponse Parameters:
NameParameterData TypeRequiredDescription
LaneIdformintNoThe lane ID.
ReadDataformstringNoThe data read by a barcode scan in Base64.
ResultformBarcodeReadResultNoThe result of the barcode scan.
SymbologyformBarcodeSymbologyNoThe symbology of the barcode read.
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.
BarcodeSymbology Parameters:
NameParameterData TypeRequiredDescription
NameformstringNo
CodeformSymbologyCodeNo

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

{"laneId":0,"aimerLightsOn":false,"image":"None","lighting":"ShorterExposure","message":"String","scanLightsOn":false,"timeout":0,"useTrigger":false}
HTTP/1.1 200 OK
Content-Type: application/json
Content-Length: length

{"laneId":0,"readData":"String","result":"Success","symbology":{"Name":"All Symbologies","Code":0},"_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"}]}