Skip to main content
Start free trialFree trial
Menu
Change language

Integration

Renttix + Samsara Integration

Pull engine hours and odometer readings from Samsara into your asset records, so service intervals, usage billing and off-hire checks are based on what the machine reports rather than what someone wrote down.

Engine hours and odometer readings straight from the machine.

A sample rental: the customer and figures are made up. The statuses and screens are Renttix’s own.

How it connects

You provide a Samsara API token from your dashboard under Settings → API tokens. Renttix supports both the US and EU Samsara hosts, so tenants with European data-residency requirements connect to the EU endpoint rather than routing readings through the US.

Once connected, readings are pulled against your assets and stored with their source recorded — telematics or manual — along with the provider they came from and the moment they were taken. That provenance matters: when a service is due or a usage charge is disputed, you can see whether the figure came from the machine or from a person.

Follow one rental

Where this happens to R-2417

A sample rental: the customer and figures are made up. The statuses and screens are Renttix’s own.

Rental recordSample

R-2417

Step 7 of 9 · Return

Location
North branch
Condition
Inspect
  1. CustomerOff-rent requested in the portal
  2. DriverPicked up: signature and photos
  3. WarehouseChecked in at North branch

Why it matters

Hours and mileage drive the economics of plant hire. They determine when a machine is serviced, what a usage-based hire costs, and whether an asset is earning or idle. Yet in most businesses these numbers are captured by someone reading a dial and writing it on a sheet — at book-out, at off-hire, sometimes neither.

The consequences run in both directions. Missed hours mean missed service intervals, which means failures on hire and warranty arguments. Understated usage means undercharging on contracts priced by the hour. And when a customer disputes a usage charge, a handwritten figure is difficult to defend. A reading pulled from the machine, timestamped and attributed, is not.

Key workflows

  • Automatic hours and odometer

    Engine hours and odometer readings are pulled from Samsara against your asset records, so utilisation and service scheduling work from machine-reported figures rather than a clipboard.

  • Book-out and off-hire capture

    Readings are recorded with the context they were taken in — routine sync, book-out, off-hire or ad hoc — so the usage across a specific hire can be established from the record rather than reconstructed.

  • EU or US data residency

    Renttix connects to either the US or EU Samsara host, so tenants with European data-residency requirements are not forced to route telematics readings through the US.

Samsara is one of three telematics options in Renttix, alongside Trackunit and the OEM-standard AEMP interface. Readings feed asset utilisation, service scheduling and usage-based billing, so telematics data reaches the commercial side of the business rather than sitting in a separate tracking portal.

Learn more about Samsara at their official website.

Visit Samsara

Samsara integration FAQ

What data does Renttix take from Samsara?

Engine hours and odometer readings against your assets, each stored with a timestamp, the provider it came from and whether the source was telematics or a manual entry. That provenance is what makes a usage charge defensible.

Can we keep telematics data in the EU?

Yes. Renttix supports Samsara's EU host as well as the US one, so tenants with European data-residency requirements connect to the EU endpoint.

How do I connect it?

Generate an API token in Samsara under Settings → API tokens and enter it in the Renttix telematics settings, choosing the appropriate regional host.

More integrations

Open your first rental record today

14-day free trial · Payments and deposits ready · Quick setup

Samsara Integration — Renttix Rental Management