Get User
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Query parameters
Include the raw data from the telematics provider. Useful for auditing or accessing fields not normalized by Catena
Response
Immutable: The datetime the record was ingested into Catena Telematics.
Unique identifier of the connection at Catena Telematics through which this record was ingested. A connection represents a Fleet/TSP pairing.
The underlying telematics platform that provided this data (e.g., samsara, motive, hos247). Note: Some platforms like hos247 offer white-labeling, so multiple TSPs may share the same source_name — use tsp_id or tsp_slug to identify the specific ELD provider.
Unique identifier of the record in the TSP. Note: we generate a unique composite key based on available fields if the TSP does not provide an unique ID.
SHA-256 hash of the source data payload. Note: we use it internally for idempotence and deduplication.
Raw source payload as ingested from the TSP. Note: use it for audit/debugging.
Datetime of when the underlying event/observation occurred, as reported by the TSP, or the moment it was ingested by us if not available in the source data.
Unique identifier for the execution that ingested this record into Catena Telematics. Note: useful for tracing.
Unique identifier for schedule that triggered this record’s execution. Note: useful for tracing.
Additional data available in the TSP (e.g., we may have external_id, provider_resource_id, etc. — this field captures all those extra attributes in a flexible way).
Unique username/login for the user (source or Catena).
Timestamp when this user record became active/in service (UTC).
Timestamp when this user record ended/out of service (UTC).
User/account status label (e.g., ‘ACTIVE’, ‘INACTIVE’, ‘SUSPENDED’).
Indicates whether the user is a driver (vs. back-office/admin).
Role/title or TSP designation (e.g., ‘DRIVER’, ‘DISPATCHER’, ‘ADMIN’).
User’s family/surname.
User’s country code (ISO-3166-1 alpha-3, e.g., ‘USA’, ‘CAN’).
Issuing country for the driver’s license (ISO-3166-1 alpha-3, e.g., ‘USA’, ‘CAN’).
Issuing region/subdivision for the license (state/province code, e.g., ‘CA’, ‘ON’).
License expiration date (YYYY-MM-DD, local to issuing authority).
Employer/HR or payroll identifier for the user (if applicable).
JSON map of company/organization group memberships (segmentation/visibility).
JSON map of user-specific private groups (per-user tags/categories).
JSON map of reporting groups (used for dashboards/permissions).
JSON map of security/role groups (authorization).
Employer/carrier name associated with the user.
Employer/carrier address associated with the user.
Carrier/company identifier as provided by the TSP (e.g., USDOT/MC or internal).
Timestamp of the user’s last login in the source TSP (UTC).
Free-text notes about the user (plain text).
Assigned HOS ruleset code for the user (normalized; see ref_hos_ruleset_codes).
Human-readable name of the HOS ruleset assigned to the user (e.g., ‘US Property (60/7)’).
Indicates whether the user is allowed to use Yard Move (YM).
Indicates whether the user is allowed to use Personal Conveyance (PC).
IANA time zone ID (e.g., ‘America/Chicago’); used as the user’s default for UI/log normalization.