Integration Guide

Before the device can be used, it needs to be registered in our system.

The device registration happens in a two-step process. At first, the device needs to call the authentication service to receive a device code and a user code. Then the registration is confirmed, entering the user code by hand.

The endpoint to request the registration is POST /oauth/token. You need to pass the client credentials and the device UUID.

Request

POST /oauth/token HTTP/1.1
Host: connect-testing.secuconnect.com
Content-Type: application/json
Accept: application/json
 
{
    "grant_type": "device",
    "client_id": "611c00ec6b2be6c77c2338774f50040b",
    "client_secret": "dc1f422dde755f0b1c4ac04e7efbd6c4c78870691fe783266d7d6c89439925eb",
    "uuid": "/vendor/unknown/cashier/dotnettest1"
}

If everything is fine, the API responds with 200 OK and some details:

Response

HTTP/1.1 200 OK
Content-Type: application/json
...
 
{
    "device_code": "2429e1d92f2f76cc3bbdc0333457ef25",
    "user_code": "aa63q9k9",
    "verification_url": "http://www.secuoffice.com",
    "expires_in": 1200,
    "interval": 5
}

The device needs to memorize the device_code in a safe place. It is used in subsequent calls.

The user_code is to be displayed, so that you can confirm the registration. You can do this in self-service in SecuOffice, or make our help desk do this for you.