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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Nash

Nash Store Locations API

Store Locations

Documentation Provider Profile APIs.io OpenAPI GitHub

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

This API exposes 12 operations across 9 paths, and defines 10 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.

12 operations 9 paths 10 schemas 1 DELETE4 GET1 PATCH6 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 Store Locations API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT, API Key) (Token).

Paths & Operations 12

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

Store Locations 12

Store Locations

POST
/v1/set_store_location_day_capacity
Set the day capacity for a store location
set_store_location_day_capacity_v1_set_store_location_day_capacity_post body → 200422
POST
/v1/set_store_location_default_capacity
Set the weekly default capacity for a store location
set_store_location_default_capacity_v1_set_store_location_default_capacity_post body → 200422
GET
/v1/store_locations
Get store locations
store_locations_v1_list_store_locations_route_get 2 params → 200422
POST
/v1/store_locations
Create store location
store_locations_v1_create_store_location_route_post body → 200422
GET
/v1/store_locations/coverage
Get store locations that cover specified location (latitude & longitude, cityzipcode)
get_store_locations_coverage_v1_store_locations_coverage_get 4 params → 200422
POST
/v1/store_locations/external-identifier/{externalIdentifier}
Create or update store location by external identifier
upsert_store_location_by_external_id_v1_store_locations_external_identifier__string_externalIdentifier__post 1 param body → 200422
GET
/v1/store_locations/external_identifier/{external_identifier}
Get store location by external identifier
store_locations_v1_get_store_location_by_external_id_route_external_identifier__string_external_identifier__get 1 param → 200422
POST
/v1/store_locations/upsert
Create or update store location
create_or_update_store_location_v1_store_locations_upsert_post body → 200422
POST
/v1/store_locations/upsert/bulk
Upsert multiple store locations
upsert_store_locations_v1_store_locations_upsert_bulk_post → 200422
GET
/v1/store_locations/{id}
Get store location
store_locations_v1_get_store_location_route__string_id__get 1 param → 200422
DELETE
/v1/store_locations/{id}
Delete store location
store_locations_v1_delete_store_location_route__string_id__delete 1 param → 200422
PATCH
/v1/store_locations/{id}
Update store location
store_locations_v1_update_store_location_route__string_id__patch 1 param body → 200422

Schemas 10

The contract defines 10 schemas that model the data the API accepts and returns. The most detailed are StoreLocationResponse (16 properties), UpdateStoreLocationInputSerializer (15 properties), CreateStoreLocationInputSerializer (14 properties), ParsedAddressInputSerializer (10 properties). Each schema is shown below with its type and property counts.

StoreLocationDefaultCapacityInputSerializer
object
Expected payload for the set store location default capacity endpoint.
2 properties 2 required
NashValidationError
object
3 properties 3 required
NashErrorDetails
object
3 properties 2 required
ListStoreLocationsResponse
object
Response for list store locations.
1 property 1 required
DeleteStoreLocationResponse
object
Layered DELETE confirmation. Returns the deleted store id and the new soft-delete flag.
2 properties 2 required
UpdateStoreLocationInputSerializer
object
Expected input payload for updating a store location.
15 properties
ParsedAddressInputSerializer
object
Parsed address input serializer for creating a job.
10 properties 3 required
StoreLocationResponse
object
Response for store location.
16 properties 8 required
CreateStoreLocationInputSerializer
object
Expected payload for creating a store location.
14 properties 2 required
StoreLocationDayCapacityInputSerializer
object
Expected payload for the set store location day capacity endpoint.
3 properties 3 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

nash-store-locations-api-openapi.yml Raw ↑

Other APIs Nash publishes across the network.

Nash AI Functions API
AE Profile APIs.io
Nash Annotate API
AE Profile APIs.io
Nash Batch Job API
AE Profile APIs.io
Nash Contracts API
AE Profile APIs.io
Nash Couriers API
AE Profile APIs.io
Nash Delivery Windows API
AE Profile APIs.io
Nash Dispatch Strategies API
AE Profile APIs.io
Nash Feedback API
AE Profile APIs.io
Nash Fleet API
AE Profile APIs.io
Nash Job API
AE Profile APIs.io
Nash Messaging API
AE Profile APIs.io
Nash Miscellaneous API
AE Profile APIs.io
#Store Locations
← Back to N APIs
API Details
ID
nash:nash-store-locations-api
Base URL
https://api.usenash.com/v1
Docs
https://docs.usenash.com/api-reference/api-overview
Provider
Nash
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=nash-store-locations-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/nash-store-locations-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have. Your account

Where this information came from

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