If some of your machines already report telematics from the factory, you don't need to put a Hapn tracker on them. An OEM provider configuration connects the manufacturer's own telematics account to Hapn, so those machines appear alongside the ones you do track — one fleet, one map, one set of reports.
Applies to: the Hapn web app at app.gethapn.com. You need access to Settings → OEM Provider Configurations, under Advanced.
Which providers can be connected
Atlas Copco, Bobcat, Cat, Hitachi, JCB, JLG ClearSky, Komatsu, Samsara, SANY, Solar Trak, Takeuchi US, TrackUnit and Vermeer.
Samsara and TrackUnit are on that list for the same reason as the manufacturers: if part of your fleet already reports into one of them, it can feed Hapn rather than being managed separately.
Before you start: get your credentials
Hapn doesn't issue these — the OEM does. You get them from that provider's developer portal or integration settings, usually under whatever partner or API agreement you already have with them. If you don't know whether your company has API access with a manufacturer, that's a question for your account contact there, not for Hapn support.
What you'll be asked for depends on the provider. Two common shapes:
- Client ID, Client Secret and Scope — for example Cat, or JLG ClearSky (where the fields are labelled Auth Client ID and Auth Client Secret). Scope defines what data Hapn is allowed to read; some providers pre-fill it with a default, which you only change if your agreement says otherwise.
- A single API key — for example Samsara, where the field is labelled with the provider's own name.
Each field has a ? icon next to it explaining what that value is, so you can check as you go.
Connect a provider
- Go to Settings → OEM Provider Configurations and select Create OEM Provider Configuration.
- Choose the OEM Provider. The credential fields below change to match it.
- Give it a Configuration Name. The suggested pattern is provider plus client — Cat - Northside Rentals — which matters if you'll connect more than one account with the same manufacturer.
- Enter the credentials.
- Select Check Credentials. Hapn tests the connection and reports back New Credentials and Fleet Size, so you can confirm it reached the right account before you commit.
- Only once that checks out, switch Enabled on — the panel says it plainly: "Enable after verifying credentials are correct."
- Select Create.
Check Credentials before enabling. It costs one click and it's the difference between finding a typo now and wondering later why nothing imported.
Reading the list
Each configuration shows as a row with:
- Configuration Name and OEM Provider — what you named it and who it connects to.
- Valid Credentials — whether the credentials still work. This is the first thing to check if machines stop updating; OEM keys can be rotated or revoked at their end without anyone telling you.
- Fleet Size — how many machines the provider reports on that account.
- Imported — how many have come into Hapn.
- Status and Last Sync — the connection's state and when it last pulled.
Fleet Size and Imported sitting far apart is the number worth watching: it means the provider knows about machines that aren't in Hapn.
Good practice
- One configuration per account, named for the account. Large operators often have several accounts with the same manufacturer.
- Treat the secret like a password. Anyone who has it can read that fleet's telematics. Hapn masks it in the form for that reason.
- Check the row after any change at the OEM's end — a renewed agreement or a rotated key shows up here as Valid Credentials failing.
Comments
0 comments
Please sign in to leave a comment.