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

Nash Zones 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 Zones. The published artifact set on APIs.io includes an OpenAPI specification, authentication docs, an AsyncAPI specification, and rate-limit docs.

This API exposes 13 operations across 9 paths, and defines 24 schemas. It is described by OpenAPI 3.2.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.

13 operations 9 paths 24 schemas 1 DELETE5 GET2 PATCH5 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
1.0.0
Base URL
https://api.usenash.com/v1
Authentication
HTTP Bearer
Resource Areas
1

Authentication & Security 1

Nash Zones API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT, API Key) (Token).

Paths & Operations 13

Across 9 paths, the API surfaces 13 operations — 1 DELETE, 5 GET, 2 PATCH, 5 POST. Each is listed below with its method, path, parameters, and response codes.

Zones 13

Zones

GET
/v1/zone-restrictions
Get zone restrictions
get_zone_restrictions_v1_zone_restrictions_get → 200422
POST
/v1/zone-restrictions
Create zone restriction
create_zone_restriction_v1_zone_restrictions_post body → 200422
POST
/v1/zone-restrictions/upsert
Upsert multiple zone restrictions
upsert_zone_restrictions_v1_zone_restrictions_upsert_post body → 200422
PATCH
/v1/zone-restrictions/{id}
Update zone restriction
update_zone_restriction_v1_zone_restrictions__string_id__patch 1 param body → 200422
GET
/v1/zones
Get zones
get_zones_list_v1_zones_get 3 params → 200422
POST
/v1/zones
Create a zone
create_zone_v1_zones_post body → 200422
GET
/v1/zones/coverage
Get zones that cover specified location (latitude & longitude, cityzipcode)
get_zones_coverage_v1_zones_coverage_get 4 params → 200422
GET
/v1/zones/external_identifier/{externalIdentifier}
Get zone by external identifier
get_zone_by_external_id_v1_zones_external_identifier__string_externalIdentifier__get 1 param → 200422
POST
/v1/zones/query
Query zones
zones_v1_query_zones_route_query_post body → 200422
POST
/v1/zones/upsert
Upsert multiple zones
upsert_zones_v1_zones_upsert_post body → 200422
GET
/v1/zones/{id}
Get zone
get_zone_v1_zones__string_id__get 1 param → 200422
DELETE
/v1/zones/{id}
Delete a zone
delete_zone_v1_zones__string_id__delete 1 param → 200422
PATCH
/v1/zones/{id}
Update a zone
update_zone_v1_zones__string_id__patch 1 param body → 200422

Schemas 24

The contract defines 24 schemas that model the data the API accepts and returns. The most detailed are StoreLocationResponse (16 properties), ZoneStoreLocationRead (13 properties), ZoneResponse (11 properties), ParsedAddressInputSerializer (10 properties). Each schema is shown below with its type and property counts.

ZonePolygonRead
object
2 properties 1 required
NashValidationError
object
3 properties 3 required
ZoneResponse
object
Response for zone.
11 properties 11 required
ZonesQueryResponse
object
Paginated zones, in created-at order. data items match GET /v1/zones/ .
2 properties 2 required
ZoneCoverageAreaRead
object
7 properties 1 required
UpdateZoneInputSerializer
object
Expected input payload for updating a zone.
7 properties
UpsertZoneRestrictionInputSerializer
object
Expected input payload for upserting a zone restriction by external id.
4 properties 1 required
ZoneStoreLocationRead
object
13 properties 1 required
ZoneLocationRead
object
9 properties
ZoneRestrictionResponse
object
Response for zone restriction.
5 properties 5 required
StoreLocationResponse
object
Response for store location.
16 properties 8 required
UpsertZonesInputSerializer
object
Expected input payload for upserting multiple zones.
1 property 1 required
UpsertZoneInputSerializer
object
Expected input payload for upserting a zone by external id.
9 properties
CreateZoneRestrictionInputSerializer
object
Expected payload for the create zone restriction endpoint.
4 properties 1 required
ZoneStoreLocationAssociationRead
object
3 properties 1 required
UpsertZoneRestrictionsInputSerializer
object
Expected input payload for upserting multiple zone restrictions.
1 property 1 required
ParsedAddressInputSerializer
object
Parsed address input serializer for creating a job.
10 properties 3 required
ZoneDetailRead
object
Full detail for a single zone. Same shape as GET /v1/zones/ .
10 properties 1 required
CreateZoneInputSerializer
object
Expected payload for creating a zone.
8 properties
NashErrorDetails
object
3 properties 2 required
PageMeta
object
Offset-pagination metadata for a single page of a query response.
3 properties 3 required
ListZoneRestrictionsResponse
object
Response for list zone restrictions.
1 property 1 required
ZonesQueryRequest
object
Body for POST /v1/zones/query. ids and externalIds are optional and combined with OR. Omit both to page through every zone in the organization; a provided but…
5 properties
ListZonesResponse
object
Response for list zones.
1 property 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nash-zones-api-openapi.yml Raw ↑

Other APIs Nash publishes across the network.

Nash AI Functions API
Nash Annotate API
Nash Batch Job API
Nash Contracts API
Nash Couriers API
Nash Delivery Windows API
Nash Dispatch Strategies API
Nash Feedback API
Nash Fleet API
Nash Job API
Nash Messaging API
Nash Miscellaneous API
Where this information came from

This is an independent, third-party profile of Nash Zones 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.