🧪 Update User
Authentication
Bearer authentication of the form Bearer <token>, where token is your auth token.
Path parameters
Query parameters
Whether to process the request synchronously. If true, Catena will attempt to create or update the resource immediately with the TSP and return the result in the response. When performing synchronous operations, you are responsible for handling any necessary retries in case of transient failures.If false (default), Catena will create an asynchronous operation, and you can check the status of the operation using the returned operation ID.
Request
Unique identifier of the connection at Catena Telematics which will be used to create this resource. A connection represents a Fleet/TSP pairing.
Unique username/login for the user (source or Catena).
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).
Carrier/company identifier as provided by the TSP (e.g., USDOT/MC or internal).
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.
DOT identifier associated with the user/carrier.
Phone country code in ’+<digits>’ format, e.g., ‘+1’.
Driver HOS compliance classification: exempt or non-exempt.
How HOS is tracked for non-exempt drivers when the source distinguishes tracking method (manual or automatic).
Response
The type of resource to operate on (e.g., vehicle, driver).
The type of operation to perform (e.g., create, update).
Immutable: The datetime the record was created in Catena Telematics.
Unique identifier of the record. Can be null for create operations where the source does not exist yet.