Configure Connection

Holman Fleet Management guide

Arrange API access with Holman Support, configure credentials and lessee codes in NIM, and test contact access.

Before you startDirect link to Before you start

API access is provided by Holman Support. You can request API documentation through the Holman API documentation request form.

NIM requires Tenant URL, Client ID, Client Secret, and Lessee Codes. Confirm with Holman Support which lessee codes and API operations are available to your integration.

Request integration access from HolmanDirect link to Request integration access from Holman

Contact Holman Support to arrange API access for your organization.
Request the API documentation using the form linked above.
Obtain the Tenant URL, Client ID, Client Secret, and authorized Lessee Codes.
Confirm the access needed for your contact, fuel PIN, and fuel transaction processes.

Enter the connection settingsDirect link to Enter the connection settings

In NIM Studio, open Systems > Overview and add a Holman Fleet Management system, or select the existing system.
Open its Connection screen.
Enter the following values and save the connection.

NIM setting	Value
Tenant URL	The Holman API tenant URL supplied for your integration.
Client ID	The client identifier issued for your API access.
Client Secret	The secret belonging to that client identifier.
Lessee Codes	The authorized lessee codes, entered in the format specified by Holman Support.

Test contact accessDirect link to Test contact access

Select Test Connection. NIM calls this endpoint on the configured tenant:
```
GET /CustomerDataAPI/contacts/basic-query?lesseeCodes={lessee_codes}&pageNumber=1&pageSize=1
```
NIM replaces {lessee_codes} with the configured Lessee Codes. The request retrieves the first page with a page size of one contact.
Confirm that the test succeeds. If it fails, verify the Tenant URL, credentials, and lessee codes with Holman Support.
Collect the system and inspect the contacts, fuelPins, and fuelTransactionsUS data needed by your process. Confirm that the returned records belong to the expected lessees.
Validate any intended contact changes with a safe test record, and check the collected fuel data before using it in reports.

The connection test reads contact data. Validate access to fuel PIN and transaction data, and any intended write operations, separately.

Step 1 of 3