Finish a device sign-in
What you can call today
Every example here runs against api.xovris.ai with a key from your account’s settings. GET /v1/health and GET /v1/public/status answer without one.
const url = 'https://api.xovris.ai/v1/device/token';const options = { method: 'POST', headers: {'Content-Type': 'application/json'}, body: '{"grant_type":"string","device_code":"string","client_id":"string"}'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request POST \ --url https://api.xovris.ai/v1/device/token \ --header 'Content-Type: application/json' \ --data '{ "grant_type": "string", "device_code": "string", "client_id": "string" }'Open to anyone, so no Idempotency-Key is kept: nobody is signed in to keep it for, and replaying one caller’s answer to another would hand it over.
No token needed: anyone may call this.
Request Body
Section titled “Request Body”object
Example
{ "grant_type": "string", "device_code": "string", "client_id": "string"}Responses
Section titled “Responses”Done.
Refused, as OAuth 2.0 says (RFC 6749, RFC 7591, RFC 8628).
An OAuth 2.0 error (RFC 6749 section 5.2; RFC 8628 section 3.5 for the device grant).
object
The standard’s code, such as invalid_request, invalid_grant, authorization_pending or slow_down.
What happened and what to do next, in plain words.
Example generated
{ "error": "example", "error_description": "example", "error_uri": "example"}Refused, as OAuth 2.0 says (RFC 6749, RFC 7591, RFC 8628).
An OAuth 2.0 error (RFC 6749 section 5.2; RFC 8628 section 3.5 for the device grant).
object
The standard’s code, such as invalid_request, invalid_grant, authorization_pending or slow_down.
What happened and what to do next, in plain words.
Example generated
{ "error": "example", "error_description": "example", "error_uri": "example"}Nothing with that id here, or it belongs to another workspace. Nothing was changed.
object
object
A stable code a program can branch on.
What happened, in plain words.
What to do next.
The recorded authorisation decision, when a role refused it.
Example generated
{ "error": { "code": "example", "message": "example", "nextStep": "example", "decisionId": "example" }}default
Section titled “default”Refused or failed: an OAuth 2.0 error from the standard’s own checks, otherwise the Problem with what to do next.
object
object
A stable code a program can branch on.
What happened, in plain words.
What to do next.
The recorded authorisation decision, when a role refused it.
An OAuth 2.0 error (RFC 6749 section 5.2; RFC 8628 section 3.5 for the device grant).
object
The standard’s code, such as invalid_request, invalid_grant, authorization_pending or slow_down.
What happened and what to do next, in plain words.
Example generated
{ "error": { "code": "example", "message": "example", "nextStep": "example", "decisionId": "example" }}object
object
A stable code a program can branch on.
What happened, in plain words.
What to do next.
The recorded authorisation decision, when a role refused it.
Example generated
{ "error": { "code": "example", "message": "example", "nextStep": "example", "decisionId": "example" }}Your data is never used to train our AI. How your data is kept
A problem is called fixed only once it works again. How each fix is checked
XOVRIS LTD, registered in England and Wales, company number 17499910. Registered office: 66 Paul Street, London EC2A 4NA.