EverPeak AI
Field notes · Samsara integration
Verified against a live org · Aug 2026
Fort Lauderdale, FL

Incident report, and what it taught us

The truck was in the yard. It was doing 50 on the turnpike.

We build fleet visibility on the Samsara API for roofing, restoration and logistics companies. This page is not a brochure. It is what we learned shipping it, including the part where we got it wrong in front of the owner.

What happened

A wall display in a restoration company's office showed a dashcam still of a truck parked in the yard, badged 5:01 PM. The truck was not in the yard. The image was three days old, and the timestamp had no date on it, so nobody could tell.

The cause was not our rendering. It was an undocumented behavior in the media endpoint, and it was hiding in every fleet we would ever connect. Everything below exists because of that afternoon.

C2C Fleet View dashboard: a satellite map of South Florida with six labelled truck markers and a trailer, a weather strip reading 74F overcast with a radar toggle, and a row of vehicle cards below showing dashcam frames with freshness timestamps.
C2C Fleet View, running. Six vehicles reporting, four moving. Note the header: dashcam stills refresh every ~6-7 min, no live video exists. The product states the platform's real ceiling rather than implying something it cannot do. Captured in demo mode, so the vehicles are synthetic and the frames are placeholders. The interface is the shipped one.

What we run today

One live dashboard for a South Florida restoration company: the whole fleet on a map with weather radar, a card per vehicle showing its newest dashcam still and exactly where it is, and a strip of the newest field photos from the job sites.

Sources

Samsara, CompanyCam, weather

Vehicles, vehicle statistics and camera media from Samsara. Job photos and projects from CompanyCam. Open-Meteo and RainViewer for conditions and radar, both keyless.

Between

Server-side proxy, no database

Every route proxies live vendor data on request. No cron, no archive, no heartbeat layer. Neither API token ever reaches the browser, and dashcam bytes are streamed rather than handing out vendor URLs.

Surface

Four wall displays

Built to be read across a room by people who are not looking for it. Allowlisted authentication. Every timestamp carries a date and a freshness verdict.

18 routes, the whole integration surface
/api/fleet · /api/fleet/feed · /api/fleet/spans · /api/vitals · /api/vehicle/[id]/detail · /api/trailer/[id]/detail
/api/camera/[id] · /api/camera/[id]/loop · /api/jobs · /api/jobs/visits · /api/jobs/[id]/photos · /api/jobsites
/api/photos · /api/weather · /api/weather/regions · /api/health · /api/auth/send-code · /api/auth/send-link
2API tokens, read only
0Databases
4Wall displays
6-7 minReal freshness ceiling
8 hrMedia URL lifetime

Field notes on the Samsara API

Verified live against a real organization in August 2026, not read from documentation. These are the things that cost us time, and the reason a second integration goes in faster than the first.

  1. The media endpoint returns the oldest frames, and ignores your limit

    /cameras/media returns at most 100 rows per response, oldest first, and silently ignores limit. We tested at 200, 512 and 1000. All three returned exactly 100.

    Both halves matter together. Ask for seven vehicles across 24 hours and you get the oldest 100 frames of that window, then it stops. The newest frame, which is the entire point of the endpoint, sits on page two. This is the bug that put a three-day-old picture on the wall. Five of seven vehicles were affected, one of them driving at the time, while a 54-minute-old frame waited on page three.

    The failure scales with how busy the fleet is. It is invisible on a quiet weekend and worst on the morning everyone is out working. Page with after=<endCursor>; hasNextPage is honest.

    Shipped this bugVerified 2026-08-11 at limit 200, 512 and 1000
  2. Rows nest one level deeper than you expect

    Media rows arrive under data.media, not data[] and not media[]. Reading one level too shallow returns undefined, which looks exactly like this fleet has no cameras, with no error raised anywhere.

    VerifiedLive org, Aug 2026
  3. vehicleIds is required, and the time range caps at one day

    Omitting vehicleIds is a 400, not an unfiltered query. Pass the roster explicitly. Windows wider than a single day also return 400.

    VerifiedLive org, Aug 2026
  4. Media URLs expire in exactly eight hours

    They carry X-Amz-Expires=28800. A URL placed in the DOM works all afternoon and breaks silently that night, which is the worst possible failure shape for a display nobody is watching. We proxy the bytes instead of handing out the URL.

    Measured28800 seconds, confirmed on response
  5. There is no live video. There are stills, every six to seven minutes

    What comes back are stills with a triggerReason of periodicStill, tripStartStill, tripEndStill or safetyEvent. That cadence is the ceiling on freshness, not your poll rate. Polling harder does not make the picture newer, and promising an owner live video is a promise the platform cannot keep.

    A parked truck simply produces no new frame. That is normal and must be rendered as normal, not as an error.

    VerifiedObserved cadence, live fleet
  6. Engine state, battery and RPM may be unlicensed, and fail silently

    On a given organization these can return empty without raising an error. Audit the license matrix before promising a customer anything beyond GPS, because the demo will work on your org and quietly show nothing on theirs.

    Promise riskOrg-dependent, check before scoping
  7. The adjacent systems have their own traps

    CompanyCam sends 0,0 for a photo with no GPS fix. That is null island, not the Gulf of Guinea, and on this fleet two of four uploaders send it on every photo because location is off on those handsets. That is half the photo volume. Guard for it anywhere coordinates become a place.

    Its per_page also caps at 50 silently, and its photo CDN URLs are public, permanent and geotagged, so anything customer-facing needs them stripped first.

    VerifiedLive org, Aug 2026

The freshness doctrine

Four rules, written the day after the wall display lied. One module decides staleness, and every surface that renders a timestamp goes through the same badge.

The doctrine, rendered

The rules above are not documentation. They are visible in the product on every card.

Vehicle cards showing per-truck location maps with speed, odometer and plate, each carrying two separate timestamps: a GPS time and a dashcam still time, with a stale badge on one truck.
Two clocks, not one. Each card carries the GPS fix time and the dashcam still time separately, because they are different ages and collapsing them is how an owner gets misled. TRUCK 4 is badged STALE at 24 minutes. TRUCK 5 reads Archived, last frame before shutdown, which is the parked-truck case rendered as normal rather than as an error. Speed, odometer and plate come straight off the vehicle statistics endpoint.

Why this matters to an owner

Nobody who runs trucks wants a dashboard. They want to stop calling people to find out where things are, and they want to trust what the screen says without walking outside to check.

That second part is the whole game. A fleet display that is wrong once is never trusted again, and the owner goes back to the phone. Which is why the unglamorous half of this page, the pagination order and the date on the timestamp, is the half that decides whether the system gets used at all.

We build the rest of the operation around it too: CRM, field photography, voice intake, scheduling and federal bid pipelines. Telematics data is most valuable when it stops being a separate screen.

The rest of the operation

Telematics is most valuable when it stops being a separate screen. The same client runs these alongside the fleet wall.

Government bidding platform shown across desktop, laptop, tablet and phone.
Federal bid pipeline. Opportunity scoring against a weighted buy box, with a shred step that catches disqualifying terms before anyone writes a proposal.
AI receptionist system shown across multiple devices.
AI receptionist. After-hours intake with a maintained knowledge base, routing to the right person instead of a voicemail box.

EverPeak AI

We build and run the operational systems that roofing, restoration and logistics companies depend on, and we are a Samsara integrator in production today. Integration-first, no hardware resale.

Andy Suarez, Founder and CEO everpeakai.com Fort Lauderdale, FL
Talk to us