Veho · Authentication Profile

Veho Authentication

Authentication

The Veho API authenticates with a static API key provided by Veho, sent on every request in an `apikey` header (UUID-shaped in the docs example). Sandbox and production use separate keys and hosts. 401 means the header was missing or the key invalid; 403 means the key lacks permission for the requested resource. GET /serviceable-zips on the sandbox host is the only documented unauthenticated endpoint. No OAuth, OIDC, or mTLS surface.

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

CompanyLogisticsShippingLast Mile DeliveryPackage TrackingeCommerceWebhooksDelivery
Methods: apiKey Schemes: 1 OAuth flows: API key in: header

Security Schemes

apiKey apiKey
· in: header (apikey)

Source

Authentication Profile

Raw ↑ 
generated: '2026-07-21'
method: searched
source: openapi/veho-api-openapi-original.yml
docs: https://docs.api.shipveho.com/docs/veho-api/jn0u5escxmisw-authentication
description: >-
  The Veho API authenticates with a static API key provided by Veho, sent on
  every request in an `apikey` header (UUID-shaped in the docs example).
  Sandbox and production use separate keys and hosts. 401 means the header
  was missing or the key invalid; 403 means the key lacks permission for the
  requested resource. GET /serviceable-zips on the sandbox host is the only
  documented unauthenticated endpoint. No OAuth, OIDC, or mTLS surface.
summary:
  types:
  - apiKey
  api_key_in:
  - header
schemes:
- name: apiKey
  type: apiKey
  in: header
  parameter: apikey
  provisioning: API keys are issued by Veho (sales/integration-led); separate key per environment
  errors:
    '401': missing or invalid apikey header
    '403': apikey lacks permission for the requested resource
  sources:
  - openapi/veho-api-openapi-original.yml