Shippit · Authentication Profile

Shippit Authentication

Authentication

Shippit secures its APIs with http across 1 declared security scheme, as derived from its OpenAPI definitions.

ShippingLogisticsFulfillmentAustraliaAPACMulti-CarrierLabelsTrackingParcelsE-commerce LogisticsSaaS
Methods: http Schemes: 1 OAuth flows: API key in:

Security Schemes

bearerAuth http
scheme: bearer

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-12'
method: derived
source: https://developer.shippit.com/dev_guide/using_apis/authentication.html
summary:
  types:
  - http
schemes:
- name: bearerAuth
  type: http
  scheme: bearer
  description: 'Per-merchant API key (referred to in Shippit docs as the API Secret)
    passed as an HTTP Bearer token: `Authorization: Bearer [example key]`. The key
    is obtained from the Shippit merchant dashboard. Shippit also recommends sending
    `user-agent` and `x-shippit-platform` headers to identify the integration. Use
    a staging key against the staging base URL (https://app.staging.shippit.com/api/3)
    and a production key against production (https://app.shippit.com/api/3). No HMAC
    request signing is documented.'
  sources:
  - https://developer.shippit.com/dev_guide/using_apis/authentication.html
  - https://developer.shippit.com/dev_guide/using_apis/using_apis.html