Skip to content
IoT OS

Resolve a stored event to a location fix

GET
/integration/v1/organizations/{organization}/devices/{uuid}/locations/{event}
curl --request GET \
  --url 'https://api.elwids.xyz/api/integration/v1/organizations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/devices/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0/locations/2489E9AD-2EE2-8E00-8EC9-32D5F69181C0?version_uuid=2489E9AD-2EE2-8E00-8EC9-32D5F69181C0' \
  --header 'Authorization: Bearer <token>'

Requires: telemetry:read

Rate limits: 240 a minute per address, 60 a minute per application

Resolves one stored telemetry event through the selected binding (version_uuid from the bindings list) with the same resolver as geofencing. data is the device runtime’s location-fix.v1 output, unchanged. 404 when the binding or the event is not found in retention; 422 when the runtime rejects the read (under errors.runtime); 503 when it is unavailable.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
organization
required
string format: uuid

The organization UUID. A value that does not match returns 404.

uuid
required
string format: uuid

A value that does not match returns 404.

event
required
string format: uuid

A value that does not match returns 404.

Query Parameters

Section titled “Query Parameters”
version_uuid
required
string format: uuid

Responses

Section titled “Responses”

200

Section titled “200”

The fix resolved through the selected binding.

Media typeapplication/json
object
version_uuid
required
string format: uuid
data
required
object
schema_version
required
Allowed value: location-fix.v1
binding_uuid
required
string format: uuid
binding_revision
required
integer
>= 1
event_id
required
string format: uuid
organization_uuid
required
string format: uuid
device_uuid
required
string format: uuid
configuration_uuid
required
string format: uuid
generation
required
integer
>= 1
evaluated_at
required
string format: date-time
observed_at
required
Any of:
string format: date-time
received_at
required
Any of:
string format: date-time
timestamp_source
required
Allowed values: source receipt corrected_future derived unknown
historical
required
boolean
status
required
Allowed values: valid unknown
reason
required
Allowed values: scope_mismatch ambiguous_parameters incomplete_fix incoherent_fix invalid_quality invalid_coordinates invalid_units invalid_time future_time untrusted_time incoherent_accuracy invalid_accuracy accuracy_required historical stale_fix eligible
live_eligible
required
boolean
point
required
Any of:
object
latitude
required
number
>= -90 <= 90
longitude
required
number
>= -180 <= 180
accuracy_metres
required
number | null

Example 

{
  "version_uuid": "2b3c4d5e-6f7a-4b8c-9d0e-1f2a3b4c5d6e",
  "data": {
    "schema_version": "location-fix.v1",
    "binding_uuid": "00000000-0000-4000-8000-000000000001",
    "binding_revision": 1,
    "event_id": "00000000-0000-4000-8000-000000000065",
    "organization_uuid": "00000000-0000-4000-8000-000000000002",
    "device_uuid": "00000000-0000-4000-8000-000000000003",
    "configuration_uuid": "00000000-0000-4000-8000-000000000004",
    "generation": 1,
    "evaluated_at": "2026-09-25T00:00:32Z",
    "observed_at": "2026-09-25T00:00:30Z",
    "received_at": "2026-09-25T00:00:31Z",
    "timestamp_source": "source",
    "historical": false,
    "status": "valid",
    "reason": "eligible",
    "live_eligible": true,
    "point": {
      "latitude": 51,
      "longitude": -114,
      "accuracy_metres": 5
    }
  }
}

Headers

Section titled “Headers”
Cache-Control
required
string
/(^|[ ,])no-store([ ,]|$)/

Responses to authenticated integration requests are never cached. The header also carries private.

Example 
no-store, private

401

Section titled “401”

No valid credentials: no session (first-party API), or a missing, invalid, expired or revoked application token (integration API).

Media typeapplication/json

The body of most error responses.

object
message
required
string

Example generated

{
  "message": "example"
}

403

Section titled “403”

The caller is not allowed: not a member of the organization, missing a tenant or platform permission, or (integration API) an ability not granted on both the application and the token.

Media typeapplication/json

The body of most error responses.

object
message
required
string

Example generated

{
  "message": "example"
}

404

Section titled “404”

Not found: an unknown organization or resource, a resource in another organization or not granted to the application, or a malformed identifier (the route does not match).

Media typeapplication/json

The body of most error responses.

object
message
required
string

Example generated

{
  "message": "example"
}

422

Section titled “422”

The input failed validation.

Media typeapplication/json

422 for input that failed validation.

object
message
required

The first error, followed by a count of the others.

string
errors
required

Messages per field, keyed by the field’s dotted path. A rejection by the device runtime appears under runtime.

object
runtime
Array<string>
key
additional properties
Array<string>

Example generated

{
  "message": "example",
  "errors": {
    "runtime": [
      "example"
    ]
  }
}

429

Section titled “429”

A rate limit was reached; see x-rate-limits on the operation.

Media typeapplication/json

The body of most error responses.

object
message
required
string

Example generated

{
  "message": "example"
}

Headers

Section titled “Headers”
Retry-After
required
integer

Seconds to wait before retrying.

503

Section titled “503”

The device runtime is not configured, unavailable, or could not complete the request.

Media typeapplication/json

The body of most error responses.

object
message
required
string

Example generated

{
  "message": "example"
}

Report a problem with this page