...
Content
| Table of Contents |
|---|
Setup
This is the documentation of how to obtain an authentication token for the ws.di.no domain.
About POST
In order to POST data into the API use a JSON object without name.
You should also set the Content-Type header to "application/json".
A request will look like this:
Curl request
| Code Block |
|---|
| Info |
|
Environments / endpoints
TEST |
| https://staging-ws.di.no/ws/json/auth/v-2/login | ||||||
PRODUCTION |
| https://ws.di.no/ws/json/auth/v-2/login |
Request object
...
Request headers
Key | Value |
|---|---|
Content-Type | application/json |
Request body
Field | Description | Example | Data type | Count |
|---|---|---|---|---|
username | The username that was provided by the DI service desk | myName | String | 1 |
password | The password that was provided by the DI service desk | secret!23 | String | 1 |
Curl request example
| Code Block |
|---|
curl https://ws.di.no/ws/json/auth/v-2/login \
-H "Content-Type:application/json" \
-d "{\"username\": \"myname\", \"password\": \"secret\"}" |
Response object
...
The endpoint replies with a response object in JSON format, containing the following data
Field | Description | Example | Data type | Count |
|---|---|---|---|---|
token | The JWT token to be used in subsequent requests | aVeryLongString | String | 1 |
The security token should be placed in theĀ Authorization header like this:
"Authorization: Bearer <token>"
The token is valid for 30 minutes and is a json web token (Ā https://jwt.io/Ā ) but can be handled as a plain string on the client side.
Changelog:
...