Skip to main content
POST
Get locomotion events for tag

Authorizations

x-auth-apikey
string
header
required

Your Rhombus API key. Must be accompanied by the x-auth-scheme header set to api-token (or partner-api-token for partner endpoints).

Headers

x-auth-scheme
enum<string>
default:api-token
required

Authentication scheme identifier. Use api-token for standard API key authentication, partner-api-token for partner API key authentication. Must be paired with the x-auth-apikey header containing your API key.

Available options:
api-token,
api,
partner-api-token,
partner-api

Body

application/json

Request object for getting locomotion events for a specified proximity tag with filtering options.

createdAfterMs
integer<int64> | null
int64

Filter events created after this timestamp in milliseconds

Example:

1640995200000

createdBeforeMs
integer<int64> | null
int64

Filter events created before this timestamp in milliseconds

Example:

1640995200000

limit
integer<int32> | null
int32

Maximum number of events to return

Example:

100

movementFilter
enum<string>

Filter events by locomotion movement type

Available options:
ARRIVAL,
DEPARTURE,
MOVED_SIGNIFICANTLY,
UNKNOWN
tagUuid
string<RUUID> | null
RUUID

base 64 (url-safe) uuid string

Example:

"AAAAAAAAAAAAAAAAAAAAAA"

Response

200 - application/json

OK

Response object containing locomotion events for a specified proximity tag.

error
boolean | null
errorMsg
string | null
locomotionEvents
object[] | null

List of locomotion events for the specified tag

warningMsg
string | null
Last modified on August 21, 2026