GET/v2/driver/{driver_id}

Get Driver by ID

Returns profile information for a single driver.

Authentication

Send both headers on every request.How auth works →

X-API-Provider-Key: Your provider key — identifies your platform. The same for every request.
X-API-Company-Key: The carrier's company key — scopes all returned data to that one carrier.

Path parameters

Parameter	Type	Description
`driver_id`	UUIDrequired	The driver's unique identifier

Responses

200OK— payload in data, wrapped in the response envelope.

Field	Type	Description
`driver_id`	UUID	Unique driver identifier
`username`	string	Driver's login username
`first_name`	string	First name
`last_name`	string	Last name
`active`	boolean	Whether the driver is currently active

401Unauthorized— missing or invalid API key.

Field	Type	Description
`status_code`	integer	HTTP status code (e.g. 401).
`description`	string	Human-readable error message.
`data`	null	Always null on error.

Sample request

curl -X GET "https://api.huntereld.com/v2/driver/d4f7b2e9-1a3c-4d8f-b5e6-2c9a7d3f1e0b" \
  -H "X-API-Provider-Key: YOUR_PROVIDER_KEY" \
  -H "X-API-Company-Key: YOUR_COMPANY_KEY"

Example response200 OK

{
  "description": "success",
  "data": {
    "driver_id": "d4f7b2e9-1a3c-4d8f-b5e6-2c9a7d3f1e0b",
    "username": "jcarter01",
    "first_name": "James",
    "last_name": "Carter",
    "active": true
  }
}

Error response401

{
  "status_code": 401,
  "description": "Company API key is not valid",
  "data": null
}