Setup Steps
DLH.io Setup Guide for Holman
Connector Pre-Requisites
This connector synchronizes your Holman fleet data: vehicles, accident claims, contacts, safety drivers, US and Canadian fuel transactions, maintenance purchase orders, odometer readings, invoices, and the documents and chassis and upfit components of each vehicle. Before you begin, make sure that you have:
- The Client ID and Client Secret that Holman issued to your company. Ask your Holman representative, or submit Holman's API User Setup form, and name the Query endpoints you need, since Holman enables endpoints on request.
- Your Holman lessee code, a 4 character code that identifies your company. A company can have more than one. Your Holman representative can give you the codes.
- Credentials for the environment you connect to. Holman first issues Staging credentials, and issues Production credentials only after you ask for them. Staging credentials do not work on Production.
Instructions (Basic Connection Setup)
DLH.io connects to Holman over secure channels using your API credentials. This connection is read only and never writes data back to Holman.
- Enter a Name or Alias for this connection, in the 'Name/Alias' field, that is unique from other connectors.
- Enter in the 'Target Schema Prefix' field, a name that will be unique in your target destination where you wish to land the data.
- Choose the Environment that your credentials belong to, Production or Staging.
- Enter the Client ID and Client Secret.
- Click Save & Test to validate the connection.
- Open the connection's source details page, go to the Configurations tab, and add one row for each lessee code. The first synchronization needs at least one.
- Optionally set a Historical Start Date on the source details page. Without one, the first synchronization reads everything Holman returns.
To move from Staging to Production, create a second connection with your Production credentials. The Environment cannot be changed on an existing connection, and each connection keeps its own data.
How Data Is Synchronized
Vehicles, contacts, accident claims, fuel, maintenance and odometer records are read as changes since the previous run, with a one hour overlap. Safety drivers and invoices are read in full on every run. The documents, chassis and upfit components of a vehicle are read for the vehicles that changed since the previous run, so a change made only to a component is picked up by a historical re-sync. Anything deleted in Holman is also picked up by a historical re-sync. Holman allows 300 requests a minute for your whole company, shared with your other integrations, and the first synchronization of a large fleet can take a while.
Holman enables each endpoint on request. A table whose endpoint is not enabled for your credentials is skipped with a warning, and loads once Holman enables it and you run a historical re-sync.