Authentication

In order to work with our api you need to use token. To retrieve new token you should use the endpoint below.

Authentication endpoint for token.

post

Authorizations

XApiKey & authorization

x-api-keystringRequired

authorizationstringRequired

Body

application/json

usernamestringRequired

Username

Example: [email protected]

passwordstringRequired

Password

Example: BIK165*

Responses

200

Success response

application/json

statusCodenumberRequiredDefault: 200

messagestringRequired

401

Unauthorized response

application/json

post

/users/login

HTTPcURLJavaScriptPython

POST /v2/users/login HTTP/1.1
Host: gw.new.skladon.net
x-api-key: YOUR_API_KEY
authorization: YOUR_API_KEY
Content-Type: application/json
Accept: */*
Content-Length: 47

{
  "username": "[email protected]",
  "password": "BIK165*"
}

{
  "statusCode": 200,
  "message": "text",
  "data": {
    "token": "eaifsagf5a44f56s4rfsd4f1a5s4f5as1f5a1s5fas5fAS5fASf",
    "expiresIn": 1715673259,
    "user": {
      "id": 1,
      "name": "Jon",
      "surname": "Doe",
      "email": "[email protected]"
    }
  }
}

Token in the response is valid till unix timestamp defined in expiresIn response atributte. The token should be used within the period. It is highly adviced to save token for later usage as it reduces API usage.

Token is valid before it expires. There can be theoretically more valid tokens for one user at the time, but it is not recommended and requesting too many tokens will be forbidden in the future.