thilak_test_api v1.0.1

thilak_test_api

ThilakTestApi - JavaScript client for thilak_test_api Swirepay REST APIs' are resource-oriented URLs that accept JSON-encoded request bodies, return JSON-encoded responses, and use standard HTTP response codes, authentication, and verbs. You can use the Swirepay API in test mode, which does not affect your live data or interact with the banking networks. The API key you use to authenticate the request determines whether the request is live mode or test mode. This SDK is automatically generated by the Swagger Codegen project:

• API version: 1.0.1
• Package version: 1.0.1
• Build package: 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 thilak_test_api --save

Local development

To use the library locally without publishing to a remote npm registry, first install the dependencies by changing into the directory containing package.json (and this README). Let's call this JAVASCRIPT_CLIENT_DIR. Then run:

npm install

Next, link it globally in npm with the following, also from JAVASCRIPT_CLIENT_DIR:

npm link

Finally, switch to the directory you want to use your thilak_test_api from, and run:

npm link /path/to/<JAVASCRIPT_CLIENT_DIR>

You should now be able to require('thilak_test_api') in javascript files from the directory you ran the last command above from.

git

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

    npm install GIT_USER_ID/GIT_REPO_ID --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, that's to say your javascript file where you actually use this library):

browserify main.js > bundle.js

Then include bundle.js in the HTML pages.

Webpack Configuration

Using Webpack you may encounter the following error: "Module not found: Error: Cannot resolve module", most certainly you should disable AMD loader. Add/merge the following section to your webpack config:

module: {
  rules: [
    {
      parser: {
        amd: false
      }
    }
  ]
}

Getting Started

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

var ThilakTestApi = require('thilak_test_api');

var defaultClient = ThilakTestApi.ApiClient.instance;

// Configure API key authorization: api_key
var api_key = defaultClient.authentications['api_key'];
api_key.apiKey = "YOUR API KEY"
// Uncomment the following line to set a prefix for the API key, e.g. "Token" (defaults to null)
//api_key.apiKeyPrefix['x-api-key'] = "Token"

var api = new ThilakTestApi.BalanceApi()

var xApiKey = "xApiKey_example"; // {String} 


var callback = function(error, data, response) {
  if (error) {
    console.error(error);
  } else {
    console.log('API called successfully. Returned data: ' + data);
  }
};
api.getBalance(xApiKey, callback);

Documentation for API Endpoints

All URIs are relative to https://staging-backend.swirepay.com/v1

Documentation for Models

• ThilakTestApi.BalanceResponse
• ThilakTestApi.CardRequest
• ThilakTestApi.CustomerRequest
• ThilakTestApi.CustomerResponse
• ThilakTestApi.DefaultResponse
• ThilakTestApi.InlineResponse200
• ThilakTestApi.InlineResponse2001
• ThilakTestApi.InlineResponse2001Entity
• ThilakTestApi.InlineResponse2002
• ThilakTestApi.InlineResponse2002Entity
• ThilakTestApi.InlineResponse2003
• ThilakTestApi.InlineResponse2004
• ThilakTestApi.InlineResponse2004Entity
• ThilakTestApi.InlineResponse2005
• ThilakTestApi.InlineResponse2006
• ThilakTestApi.InlineResponse2006Entity
• ThilakTestApi.InlineResponse200Entity
• ThilakTestApi.PaymentMethodRequest
• ThilakTestApi.PaymentMethodRequestCard
• ThilakTestApi.PaymentMethodResponse
• ThilakTestApi.PaymentSessionResponse
• ThilakTestApi.UserResponse

Documentation for Authorization

api_key

• Type: API key
• API key parameter name: x-api-key
• Location: HTTP header