🧪 Update Trailer
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.
Manufacturer (OEM) of the trailer.
Manufacturer model or type designation (e.g., ‘53ft Dry Van’, ‘Reefer’).
Model year (four-digit, e.g., 2022).
Vehicle Identification Number (VIN), typically 17 characters; if available.
Plate region/subdivision (state/province code, e.g., ‘CA’, ‘ON’).
Plate country code (ISO-3166-1 alpha-2, e.g., ‘US’, ‘CA’).
License plate number (e.g., ‘HMT-3570’).
Indicates whether this trailer is currently active/in service.
Operational status label (e.g., ‘IN_SERVICE’, ‘OUT_OF_SERVICE’, ‘MAINTENANCE’).
Free-text notes about the trailer (plain text).
Telematics/ELD device identifier associated with this trailer, if any.
Telematics/ELD device serial number, if any.
Telematics/ELD device type or model family (vendor-specific).
Telematics/ELD vendor product identifier (catalog/model code).
Length of the trailer (numeric; unit per source, e.g., feet or meters).
Body type/classification (e.g., Dry Van, Reefer, Flatbed, Tanker, Chassis).
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.