Nash Fleet API
Inbound endpoints fleets call to update in-flight deliveries.
Nash Fleet API is one of 30 APIs that Nash publishes on the APIs.io network, described by a machine-readable OpenAPI specification and an AsyncAPI event-driven specification.
Tagged areas include Fleet. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, an AsyncAPI specification, and rate-limit docs.
This API exposes 2 operations across 2 paths, and defines 20 schemas. It is described by OpenAPI 3.1.0, at version 1.0.0.
Requests are made against 4 base URLs: https://api.sandbox.usenash.com, https://api.sandbox.ap-southeast-2.usenash.com, https://api.usenash.com, https://api.ap-southeast-2.usenash.com.
Metadata
The identity and technical contract details declared by the specification.
Authentication & Security 1
Nash Fleet API declares
1 security scheme
for authenticating requests.
It accepts HTTP bearer tokens (JWT, API Key) (Token).
Paths & Operations 2
Across 2 paths, the API surfaces 2 operations — 2 PATCH. Each is listed below with its method, path, parameters, and response codes.
Inbound endpoints fleets call to update in-flight deliveries.
Schemas 20
The contract defines 20 schemas that model the data the API accepts and returns. The most detailed are DeliverySerializer (34 properties), BarcodeInfoSerializer (15 properties), BulkDeliveryUpdateItem (14 properties), PickedItemsSerializer (12 properties). Each schema is shown below with its type and property counts.
Specification
The full machine-readable OpenAPI contract behind this narrative.
Source
More from Nash 12
Other APIs Nash publishes across the network.