Legacy Partner Integration (v1)
The original partner-integration API — issues a ClientKey to a predefined integration partner, scoped to specific data modules.
Two key systems
This is the legacy integration API. New integrations should prefer the
modern Public API keys
(ezt_live_…) with granular scopes. The legacy API remains available for the
predefined partners listed below.
Base URL
Integration API host
https://integration.test.eztotrack.com/api/v1 (test). Management endpoints below
are relative to this base.
Authentication
Integration management calls (creating/listing/deleting integrations) are made from the dashboard and authenticated with your normal account Authorization: Bearer <JWT>. The company is taken from the token.
The generated ClientKey is the credential the partner presents when pulling your data.
Endpoints
| Method | Path | Description |
|---|---|---|
| GET | /Integration?active=true | List the company's integrations (optionally filter by integrator). |
| POST | /Integration | Create an integration. Returns the object including the generated clientKey. |
| PUT | /Integration | Update an integration (e.g. change allowed data modules). |
| DELETE | /Integration/{id}?clientKey={clientKey} | Revoke an integration. |
Partners (integrator)
| Value | Partner |
|---|---|
| 0 | Project44 |
| 1 | TrackerTools |
| 2 | Schenker |
| 3 | FourKites |
| 4 | Highway |
| 5 | Waste |
| 6 | BrightOrder |
| 7 | MDN |
Each partner may be integrated once per company.
Data modules (allowedData)
| Value | Module | Requires |
|---|---|---|
| 6 | Location and cargo | — |
| 7 | Waste Management | Waste Management feature |
| 8 | HOS (ELD) | ELD feature |
Create an integration
POST /api/v1/Integration
Authorization: Bearer <your-dashboard-JWT>
Content-Type: application/json
{
"integrator": 3,
"allowedData": [6]
}Response (the clientKey is what you give the partner):
{
"id": "65f0c1a2b3d4e5f6a7b8c9d0",
"companyId": 7,
"integrator": 3,
"allowedData": [6],
"clientKey": "b1946ac92492d2347c6235b4d2611184",
"utcIssuedOn": "2026-02-14T11:14:28.307Z",
"issuedBy": "admin@acme.com",
"active": true
}Revoking
There is no key rotation — to issue a new clientKey, delete the integration and create it again.
Next: call the data API
Once a partner has a ClientKey, they exchange it for a token and call the data endpoints — see Legacy Data API.