How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Track-POD Driver API

The Driver API from Track-POD — 3 operation(s) for driver.

Track-POD Driver API is one of 8 APIs that Track-POD publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 2 JSON Schema definitions.

Tagged areas include Driver. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 7 operations across 3 paths, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 2.0.

Requests are made against a single base URL, https://api.track-pod.com.

7 operations 3 paths 4 schemas 2 DELETE3 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
2.0
Base URL
https://api.track-pod.com
Authentication
API Key
Resource Areas
1

Authentication & Security 1

Track-POD Driver API declares 1 security scheme for authenticating requests. An API key is passed in the header as X-API-KEY (ApiKey). By default, every request must be authenticated.

  • ApiKey — Please enter API key into field

Paths & Operations 7

Across 3 paths, the API surfaces 7 operations — 2 DELETE, 3 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Driver 7
GET
/Driver/Id/{id}
Get driver by Track-POD unique identifier
GetDriverById 1 param → 200401404429500
DELETE
/Driver/Id/{id}
Delete driver by Track-POD unique identifier
DeleteDriverById 1 param → 200400401404429500
GET
/Driver/Username/{username}
Get driver by Username
GetDriverByUsername 1 param → 200401404429500
DELETE
/Driver/Username/{username}
Delete Driver by id.
DeleteDriverByUsername 1 param → 200400401404429500
GET
/Driver
Get drivers
GetDrivers → 200401429500
POST
/Driver
Add driver
AddDriver body → 201400401405415429500
PUT
/Driver
Update driver
UpdateDriver body → 202400401404405415429500

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Driver (13 properties), UpdateDriver (12 properties), NewDriver (11 properties), ApiResponse (3 properties). Each schema is shown below with its type and property counts.

UpdateDriver
object
12 properties
ApiResponse
object
Object for all API responses, except GET (status code: 200)
3 properties
Driver
object
13 properties
NewDriver
object
"" - required fields
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

track-pod-driver-api-openapi.yml Raw ↑

Other APIs Track-POD publishes across the network.

Track-POD Address API
Track-POD Order API
Track-POD RejectReason API
Track-POD Route API
Track-POD Test API
Track-POD Vehicle API
Track-POD VehicleCheck API
Where this information came from

This is an independent, third-party profile of Track-POD Driver API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.