Skip to main content
Use GET /ping as your first call whenever you set up a new integration or rotate an API key. It confirms your key is active, tells you which account it belongs to, and lists the scopes it carries — all without touching any merchant data.

Authentication

Send your API key as a Bearer token or in the X-Api-Key header. No additional scope is needed.
When you include the X-Merchant-Id header, the response also contains an activeMerchant object with the resolved merchant’s details. This is useful for confirming that a merchant ID you intend to use is correctly linked to your company account.

Request

Basic health check

With merchant context

Response

200 — Success

string
API version string — always "Now Shipping Public API v1".
object
Details of the business account associated with this API key.
string[]
Scopes enabled on this key — any combination of orders, pickups, and merchants.
string
Key prefix, always nsk_live for production keys.

Errors

Run GET /ping as a startup check in your service. If it returns 401, stop immediately and alert your team — do not proceed to create orders with an invalid key.