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 Route API

The Route API from Track-POD — 24 operation(s) for route.

Track-POD Route 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 Route. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, and 2 JSON Schemas.

This API exposes 28 operations across 24 paths, and defines 18 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.

28 operations 24 paths 18 schemas 2 DELETE7 GET2 PATCH1 POST16 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 Route 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 28

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

Route 28
POST
/Route
Add route
AddRoute 4 params body → 201202400401405415429500
PUT
/Route/Code/{code}
Update route by code
UpdateRouteByCode 3 params body → 200202400401404405429
GET
/Route/Code/{code}
Get route by code
GetRouteByCode 1 param → 200401404429500
DELETE
/Route/Code/{code}
Delete route by code.
DeleteRouteByCode 2 params → 200400401404429500
PUT
/Route/Id/{id}
Update route by id
UpdateRouteById 3 params body → 200202400401404405429
GET
/Route/Id/{id}
Get route by id
GetRouteById 1 param → 200401404429500
DELETE
/Route/Id/{id}
Delete route by id.
DeleteRouteById 2 params → 200400401404429500
PATCH
/Route/Code/{code}/CustomFields
Update routes custom fields by route code
UpdateRouteCustomValuesByCode 1 param body → 200202400401404405429
PATCH
/Route/Id/{id}/CustomFields
Update routes custom fields by route id
UpdateRouteCustomValuesById 1 param body → 200202400401404405429
GET
/Route/Date/{date}
Get routes by date
GetRouteByDate 1 param → 200400401429500
GET
/Route/Export/Code
Get route codes for export (exported is False)
GetRouteExportCode 1 param → 200400401429500
GET
/Route/Export/Id
Get route ids for export (exported is False)
GetRouteExportId 1 param → 200400401429500
PUT
/Route/Export/Code/{code}
Confirm route export (set exported to True) by code
SetRouteExportCode 1 param → 202401429500
PUT
/Route/Export/Id/{id}
Confirm route export (set exported to True) by id
SetRouteExportId 1 param → 202401429500
PUT
/Route/Code/{code}/Order
Add new order to route
AddOrderToRouteByCode 3 params body → 202400401405415429500
PUT
/Route/Id/{id}/Order
Add new order to route
AddOrderToRouteById 3 params body → 202400401405415429500
PUT
/Route/Code/{code}/Order/Number/{number}
Add existing order to route
MoveOrderToRouteByCodeByNumber 4 params → 202400401404405429500
PUT
/Route/Code/{code}/Order/Id/{orderId}
Add existing order to route
MoveOrderToRouteByCodeById 4 params → 202400401404405429500
PUT
/Route/Id/{id}/Order/Number/{number}
Add existing order to route
MoveOrderToRouteByIdByNumber 4 params → 202400401404405429500
PUT
/Route/Id/{id}/Order/Id/{orderId}
Add existing order to route
MoveOrderToRouteByIdById 4 params → 202400401404405429500
GET
/Route/Track/Code/{code}
Get route track by code
GetRouteTrackByCode 1 param → 200400401404429500
GET
/Route/Track/Id/{id}
Get route track by id
GetRouteTrackById 1 param → 200401404429500
PUT
/Route/Start/Code/{code}
Start route by code
StartRouteByCode 2 params → 200202400401404405429
PUT
/Route/Start/Id/{id}
Start route by id.
StartRouteById 2 params → 200400202401404405429
PUT
/Route/Close/Code/{code}
Close route by code
CloseRouteByCode 2 params → 200202400401404405429
PUT
/Route/Close/Id/{id}
Close route by id.
CloseRouteById 2 params → 200400202401404405429
PUT
/Route/Ready/Code/{code}
Set route ready by code.
SetRouteReadyByCode 2 params → 200202400401404429
PUT
/Route/Ready/Id/{id}
Set route ready by id.
SetRouteReadyById 2 params → 200400202401404405429

Schemas 18

The contract defines 18 schemas that model the data the API accepts and returns. The most detailed are Order (83 properties), PickupOrder (63 properties), NewOrder (35 properties), Route (28 properties). Each schema is shown below with its type and property counts.

NewOrder
object
"" - required fields
35 properties
NewRoute
object
16 properties
NewOrderGoods
object
"" - required fields
9 properties
PickupOrder
object
63 properties
RouteTrack
object
1 property
Vehicle
object
6 properties
NotificationsPolicy
object
4 properties
Goods
object
17 properties
RouteTrackPoint
object
4 properties
RouteStatus
string
LoadStatus
string
CustomField
object
3 properties
Route
object
28 properties
NewPickupOrder
object
16 properties
ApiResponse
object
Object for all API responses, except GET (status code: 200)
3 properties
Source
string
Order
object
83 properties
NewCustomField
object
2 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

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

Other APIs Track-POD publishes across the network.

Track-POD Address API
Track-POD Driver API
Track-POD Order API
Track-POD RejectReason 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 Route 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.