qsr_pos_api v0.0.0

qsr_pos_api

QsrPosApi - JavaScript client for qsr_pos_api No description provided (generated by Swagger Codegen https://github.com/swagger-api/swagger-codegen) This SDK is automatically generated by the Swagger Codegen project:

• API version: 0.0.0
• Package version: 0.0.0
• Build package: class io.swagger.codegen.languages.JavascriptClientCodegen

Installation

For Node.js

npm

To publish the library as a npm, please follow the procedure in "Publishing npm packages".

Then install it via:

npm install qsr_pos_api --save

git

If the library is hosted at a git repository, e.g. https://github.com/YOUR_USERNAME/qsr_pos_api then install it via:

    npm install YOUR_USERNAME/qsr_pos_api --save

For browser

The library also works in the browser environment via npm and browserify. After following the above steps with Node.js and installing browserify with npm install -g browserify, perform the following (assuming main.js is your entry file):

browserify main.js > bundle.js

Then include bundle.js in the HTML pages.

Getting Started

Please follow the installation instruction and execute the following JS code:

var QsrPosApi = require('qsr_pos_api');

var api = new QsrPosApi.DefaultApi()

var checkNumber = 56; // {Number} The check number

var opts = { 
  'qSRPOSMessageUID': "qSRPOSMessageUID_example" // {String} 
};

var callback = function(error, data, response) {
  if (error) {
    console.error(error);
  } else {
    console.log('API called successfully.');
  }
};
api.checksCheckNumberCoursesBumpsPost(checkNumber, opts, callback);

Documentation for API Endpoints

All URIs are relative to http://192.168.180.50:32768/pos

Documentation for Models

• QsrPosApi.ActivityLevel
• QsrPosApi.ActivityLevelList
• QsrPosApi.Check
• QsrPosApi.Course
• QsrPosApi.CoursePaymentState
• QsrPosApi.Item
• QsrPosApi.ItemCancellation
• QsrPosApi.ItemList
• QsrPosApi.ItemModifiers
• QsrPosApi.RuntimeInformation
• QsrPosApi.Server
• QsrPosApi.TableCheckStatus
• QsrPosApi.TableLocatorEvent
• QsrPosApi.TableStatus

Documentation for Authorization

All endpoints do not require authorization.