Navigate WMS
  1. Authentication
Navigate WMS
  • Navigate WMS
    • Introduction
  • Authentication
    • Authentication API
    • Authenticate User
      POST
  • Locations
    • Locations API
    • Get Locations
      GET
    • Add Location
      POST
    • Update Location
      PUT
    • Get Prep Locations
      GET
  • Product Catalog
    • Product Catalog API
    • Get Products
      POST
    • Add Product
      PUT
    • Get Product Details
      GET
    • Update Product
      PUT
    • Activate/Deactivate Product
      PATCH
    • Get Bundles
      POST
    • Add Bundle
      PUT
    • Get Bundle Details
      GET
    • Update Bundle
      PUT
    • Activate/Deactivate Bundle
      PATCH
    • Get Supplies
      POST
    • Add Supply
      PUT
    • Get Supply Details
      GET
    • Update Supply
      PUT
    • Activate/Deactivate Supply
      PATCH
    • Get Items
      POST
  • Inventory
    • Inventory API
    • Get Inventory
    • Get Inventory Details
  • Orders
    • Get Inbound Orders
    • Create Inbound Order
    • Get Inbound Order Details
    • Update Inbound Order
    • Cancel Inbound Order
    • Get Prep Orders
    • Create Prep Order
    • Get Prep Order Details
    • Update Prep Order
    • Cancel Prep Order
    • Get Manual Orders
    • Create Manual Order
    • Get Manual Order Details
    • Update Manual Order
    • Cancel Manual Order
  • Miscellaneous
    • Get Package Types
    • Get Prep Services
  1. Authentication

Authentication API

Users must authenticate themselves and obtain an authentication token
before invoking the Navigate APIs. Authentication must be performed
using the username and password selected at the time of registration.
For example, if a user registered with the username john@acme.com
and password SampleP4ss, this same username-password combination
should be used for obtaining an authentication token for the APIs.
The authentication token must be sent with every subsequent API request
as a bearer token. This is done by including the HTTP header named
Authorization with the value Bearer [authentication token]. For
instance, if the authentication token obtained from the Authentication
API is
eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.KMUFsIDTnFmyG3nMiGM6H9FNFUROf3wh7SmqJp-QV30
it should be sent with subsequent API requests as
Authorization: Bearer eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJzdWIiOiIxMjM0NTY3ODkwIiwibmFtZSI6IkpvaG4gRG9lIiwiYWRtaW4iOnRydWUsImlhdCI6MTUxNjIzOTAyMn0.KMUFsIDTnFmyG3nMiGM6H9FNFUROf3wh7SmqJp-QV30
Each authentication token is valid for 60 minutes (1 hour) and must be
obtained again once it expires.
Modified at 2025-10-28 05:23:45
Previous
Introduction
Next
Authenticate User
Built with