Atlas API — getting started

The Atlas API is a normal REST API. Bearer-token auth, JSON payloads, stable contracts.

Generate a key

Dashboard → Developer → API keys → Create. Two keys per workspace:

test — Shippo test mode, no real money
live — production

Both start with atl_.

Auth

Authorization: Bearer atl_live_abc123...

Get a rate

curl https://api.atlasbridgelogistics.com/v1/parcel/rates \
  -H "Authorization: Bearer atl_live_..." \
  -H "Content-Type: application/json" \
  -d '{
    "from": { "name": "Acme", "street1": "100 Main St", "city": "Brooklyn", "state": "NY", "postal_code": "11201", "country": "US" },
    "to":   { "name": "Jane Doe", "street1": "500 Pine Ave", "city": "Seattle", "state": "WA", "postal_code": "98101", "country": "US" },
    "parcels": [ { "length_in": 10, "width_in": 8, "height_in": 4, "weight_lb": 2 } ]
  }'

Buy a label

curl https://api.atlasbridgelogistics.com/v1/parcel/shipments \
  -H "Authorization: Bearer atl_live_..." \
  -d '{ "rate_id": "rate_abc123..." }'

Response: tracking_number, label_url, plus full shipment object.

Track

curl https://api.atlasbridgelogistics.com/v1/tracking/1Z123... \
  -H "Authorization: Bearer atl_live_..."

Webhooks

Register an HTTPS endpoint in Developer → Webhooks. HMAC-SHA256 signed JSON (Atlas-Signature: t=...,v1=... — same as Stripe).

Rate limits

60 req/sec per workspace
10,000 req/day on starter
429 returns Retry-After