Query raw ingestion metadata as a platform administrator.
const url = 'https://api.dev.iot-sens.schlossers.at/v1/raw-ingestion-messages?processingStatus=accepted&scope=all&limit=25';const options = {method: 'GET', headers: {Authorization: 'Bearer <token>'}};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url 'https://api.dev.iot-sens.schlossers.at/v1/raw-ingestion-messages?processingStatus=accepted&scope=all&limit=25' \ --header 'Authorization: Bearer <token>'Returns 25 reverse-chronological metadata records at a time without an
exact total. to is the fixed upper investigation anchor, and every
continuation must reuse it and all active filters. Exact MQTT and sensor
payloads are deliberately excluded and loaded only through the detail
operation. Responses are not cacheable.
Authorizations
Section titled “Authorizations”Parameters
Section titled “Parameters”Query Parameters
Section titled “Query Parameters”Defaults to 24 hours before to; the bounded range may not exceed 42 days.
Fixed upper investigation anchor; defaults to current server time and continuations reuse it.
Exact case-normalized Netmore topic customer.
Trusted registry-derived tenant scope, never the Netmore customer value.
Opaque continuation token; reuse the original filters and scope.
Number of timeline records to return; defaults to 25, accepts 1 through 100, and is bound into continuation cursors.
Responses
Section titled “Responses”Reverse-chronological raw-ingestion metadata page.
object
object
Example
{ "items": [ { "processingStatus": "accepted", "mqttQos": 0, "rawPayloadEncoding": "base64" } ]}Headers
Section titled “Headers”default
Section titled “default”A safe platform error response.
object
object
Example
{ "error": { "code": "VALIDATION_FAILED", "category": "validation" }}