Page History
...
Below table describes currently available report export endpoints and their differences on a higher level and allows you user to choose the best option for your the requirements.
Endpoint | Method | Request Format | Allows multiple reports to be exported in a single request | Allows filtering for reports | Description | |
---|---|---|---|---|---|---|
Export reports | /report/export/{uuid} | GET | N/A | Export a single report with its UUID. | ||
Export reports (GET) | /report/export?@imei={imei} | GET | N/A | Export past month's reports with optional IMEI filtering. | ||
Export reports (POST) | /report/export | POST | application/json | Export reports with the filters/options provided in the request body. |
...
Export reports with the options provided in the request body. Allows user to define more defined search criteria and only return matching reports.
Supported report fields
Field name | XML field path | Name |
---|---|---|
IMEI | blancco_hardware_report.system.imei | @imei |
System Serial | blancco_hardware_report.system.serial | @system_serial |
Erasure State | blancco_erasure_report.erasures.erasure.state | @erasure_state |
Custom field | user_data.fields.{CUSTOM_FIELD_NAME} | @custom-{CUSTOM_FIELD_NAME} |
Code Block | ||
---|---|---|
| ||
{
"filter": {
"date": {
"gte": "2023-01-01T00:00:00Z"
},
"fields": [
{
"name": "@imei",
"like": "123456789012345"
},
{
"name": "@custom-my custom field",
"like": "my custom field value"
}
]
},
"category": "ERASURE",
"format": "XML",
"container": "ZIP"
} |