Using your clientKey and clientSecret you can request for a token by calling the dedicated method (note: replace asterisks with your clientKey and clinetSecret)
curl
Copy /curl -X POST \
https://explore.cloud4wi.com/v1/sts/login/services \
-H 'Cache-Control: no-cache' \
-H 'Content-Type: application/json' \
-H 'accept: application/json' \
-d '{
"clientKey":"ck-********-****-****-****-************",
"clientSecret":"********************************"
}'/curl -X POST \
If the client key and secret are correct, then the API will return a JWT token.
Copy {"token":[[JWT_TOKEN]]"}
curl
Copy curl -X GET \
'https://explore.cloud4wi.com/v2/customers/organizations/[[CID]]?sortBy=created_absolute&sortReverse=false' \
-H 'Authorization: Bearer [[JWT_TOKEN]]' \
-H 'Cache-Control: no-cache' \
-H 'accept: application/json'
The JWT token expires after one day ; to get a new one, restart and call again /v1/sts/login/services.
AuthN/AuthZ Flow
Endpoints
Use your client key and client secret to retrieve a valid authentication token
Get authentication token
post
https://explore.cloud4wi.com/ /v1/sts/login/services Returns a JWT token inside the body and in the Authorization Header of the response
clientSecret string Optional
Response object
Show properties
Copy POST //v1/sts/login/services HTTP/1.1
Host: explore.cloud4wi.com
Content-Type: application/json
Accept: */*
Content-Length: 42
{
"clientKey": "text",
"clientSecret": "text"
}
You can manually revoke a token using the following end-point:
Revoke authetnication Token
post
https://explore.cloud4wi.com/ /v1/sts/logout It revokes the JWT token passed in the header.
200 The token has been revoked
401 The token is not valid
Copy POST //v1/sts/logout HTTP/1.1
Host: explore.cloud4wi.com
Authorization: Bearer JWT
Accept: */*
Last updated 10 months ago