After successful authentication, the following call tells the client, that a device token can be registered and used afterward.

HTTP Request: Get registered device tokens

copy

GET /auth-login/rest/protected/my/tokens/device-tokens/

HTTP Response: Empty list of device tokens

copy

HTTP/1.1 200 OK

{
    "meta": {
        "type": "jsonapi.metadata.document",
        "timestamp": "2018-02-12T17:52:15.634+01:00"
    },
    "data": []
}

The return code "200" signals that the device token feature is enabled and device tokens can be registered.

Other return codes signal, that device tokens cannot be registered:

• ●
  501: not configured
• ●
  403: user is not allowed to register device tokens (missing authentication or too little privileges)
• ●
  404: IAM server is too old to know about the device token feature (or the URL is wrong)