The K2 API is a full RESTful API. The API is based on a full REST resource model. Each resource is given a URI (Unique Resource Identifier), and the operation is determined by a HTTP Request Method (GET/POST/PATCH etc).
The outcome of each operation is defined by standard HTTP response code (i.e. 200 – Success, 403 – Forbidden, etc.).
MG+ K2 Common Wallet API Reference
Detailed and up-to-date K2 API methods documentation is available on the DevPortal at the following URL: https://devportal.k2net.io/.
Access to the documentation is restricted by IP whitelisting. Please contact your account manager to whitelist your IP address.
K2 API Access
Endpoint
To access the K2 API each client receives a dedicated URL address from MG+.
This address is marked as <API-HOST> in this documentation. The access protocol for the K2 API is HTTPS.
The endpoint address is constructed as follows: https://<API-HOST>/api/
The API Version for this document is: 1
Authentication & Authorization
Access to the K2 API is controlled by authenticating and authorizing requests using a valid access token obtained from the STS.
The token should be applied as a request header in the following format:
Authorization: Bearer <token>
Request Parameters Submission
The K2 API methods use two templates to post data:
|
Type |
|
Note |
|---|---|---|
|
Forms |
application/x-www-formurlencoded |
All methods that accept key/value pairs of parameters. This is the default format. |
|
JSON |
application/json |
All methods that accept input parameters as objects. |