Skip to content

Get started

Authentication

Each operation declares its supported security scheme in the API reference. Seller Shipping Labels accepts either a bearer token in the Authorization header or an authenticated accessToken cookie.

Use credentials issued for the Gearment team that owns the seller account. API access is evaluated against that authenticated team.

REST endpoints

Seller Shipping Labels uses JSON over HTTPS at the POD API server. Use the public resource paths in the API reference; no Connect protocol headers are required.

GET /pod/v1/vendor/shipping-labels/services HTTP/1.1
Host: apiv2.gearment.com
Authorization: Bearer YOUR_ACCESS_TOKEN
Accept: application/json

Integration checklist

  1. Authenticate as the intended Gearment seller team.
  2. Call GET /v1/vendor/shipping-labels/services to confirm the team's available carriers and services.
  3. Create a rate quote with POST /v1/vendor/shipping-labels/rates before requesting a purchase.
  4. Use a unique requestId when purchasing a label so retries remain idempotent.
  5. Store the returned label identifier and retrieve the label from Gearment when it is needed by your workflow.