Response Format
Callback Response
When using the callback option, results are returned in this format:
{
"type": "com.deviceassure.payload.result",
"data": {
"code": "bd3f41f0-ace0-4c77-ae33-da195f2675ff",
"deviceAssure": {
"result": "AUTHENTIC",
"reason": "Device has passed all verification checks",
"deviceAtlasProperties": {
"vendor": "Google",
"marketingName": "Pixel 6a"
},
"referenceId": "871d26e2-94fb-400a-92ab-3b9a672b4c53"
},
"meta": {}
}
}
| Property | Type | Description |
|---|---|---|
type | string | Response type: com.deviceassure.payload.result, com.deviceassure.payload.redirect, or com.deviceassure.payload.reload |
data.code | string | Unique QR code identifier |
data.deviceAssure | object | Device verification result (see API Response for details) |
Redirect Response
When using redirect or deviceRedirect, the target URL receives a response query parameter containing a base64-encoded JSON string:
The decoded response has a flattened structure (no type or data wrapper):
{
"code": "bd3f41f0-ace0-4c77-ae33-da195f2675ff",
"deviceAssure": {
"result": "AUTHENTIC",
"reason": "Device has passed all verification checks",
"deviceAtlasProperties": {
"vendor": "Google",
"marketingName": "Pixel 6a"
},
"referenceId": "871d26e2-94fb-400a-92ab-3b9a672b4c53"
},
"meta": {}
}
Use DeviceAssure.parseQrRedirect() to decode the response. See Methods for usage details.
See Also
- Methods - Available QR code methods
- Examples - Implementation examples
- API Response - Full API response documentation