← Back to all docs

Shippit API

Shippit is an Australian commerce delivery platform that automates carrier selection and optimizes last-mile logistics across 100+ carriers. An unofficial API lets you programmatically retrieve quotes, create and cancel orders, book carriers, pull shipping labels, and track shipments—and push updates like webhook subscriptions, returns, and merchant settings back into Shippit.

By Alex KlarfeldMay 30, 2026
Shippit API

What is Shippit?

Shippit is a commerce delivery platform that automates shipping decisions and optimizes last-mile logistics across 100+ carriers and own-fleet operations. Retailers use Shippit to present checkout delivery options, allocate carriers, book and label shipments, track parcels, manage returns, and run their own delivery fleet—integrating with ecommerce platforms and WMS/ERP/OMS systems through ready-to-go connectors and the Shippit APIs.

Core product areas include:

  • Multi-Carrier Shipping (carrier connectivity, checkout delivery options, shipping automation, fulfillment)
  • NowGo Fleet Management (dispatch, route optimization, driver management)
  • Shippit Intelligence (AI-powered decisioning and optimization)
  • Data & Reporting (analytics, insights, performance metrics)

Common data entities:

  • Orders, Bookings, Order Groups, Consolidations
  • Quotes, Service Levels, Carrier Allocations, Pricing
  • Shipments, Tracking Events, Proof of Delivery, Estimated Delivery Dates
  • Labels, Parcels, Dangerous Goods, International Orders
  • Returns Requests, Return Notifications, Returns Portal records
  • Merchant Settings, Operating Hours, Webhooks

The Shippit Integration Challenge

Retailers run mission-critical fulfillment on Shippit every day, but turning store-level configuration and carrier workflows into reliable API-driven automation is non-trivial:

  • Per-store API keys: Each store has its own unique API key generated only after payment details are added, so multi-store and multi-region setups must manage many credentials
  • Multi-carrier variability: Quotes, service levels, and tracking semantics differ across 100+ carriers, and generic integrations break when carrier behavior shifts
  • Order-flow sequencing: Quote, order, book, and label steps must be orchestrated in the right order, with consolidation and order grouping adding state to manage
  • Push vs. pull tracking: Status can arrive via the /track endpoint or via webhooks, and keeping both paths consistent requires deduplication and reconciliation
  • Returns and merchant settings: Returns portal workflows and merchant configuration (operating hours, webhook registration) sit behind separate APIs with their own request shapes
  • Separate NowGo surface: Own-fleet dispatch and routing live in a distinct NowGo API, so fleet and carrier data must be stitched together

How Supergood Creates Shippit APIs

Supergood reverse-engineers Shippit's authenticated API surfaces—the multi-carrier shipping APIs and the NowGo fleet APIs—to deliver a resilient, normalized API layer for your Shippit account across stores and regions.

  • Manages per-store API keys securely and routes calls to the right store and region
  • Orchestrates the quote → order → book → label → track flow with retries and idempotency
  • Normalizes responses across carriers, shipments, labels, and returns so you integrate once and rely on consistent objects
  • Reconciles pull-based /track results with push-based webhook events for a single source of truth

Use Shippit with AI agents: Shippit MCP Server →

Getting Started

  • Schedule Integration Assessment

Book a 30-minute session to confirm your stores, carriers, and fulfillment workflows.

  • Supergood Generates and Validates Your API

We deliver a production-ready Shippit adapter tailored to your store configuration and carrier mix.

  • Deploy with Monitoring

Go live with continuous monitoring and automatic adjustments as Shippit and its carriers evolve.

shippit

API Endpoints

Authentication

POST/authenticate

Authenticate with a store-specific Shippit API key and establish a managed session for downstream calls.

Quoting

POST/quotes

Request quotes across carriers and service levels using delivery address, origin, and parcel dimensions.

Orders

POST/orders

Create an order with delivery details, parcels, and selected service level, optionally grouping or consolidating orders.

Orders

GET/orders

Retrieve orders and their current status, with filters for date, store, and fulfillment state.

Fulfillment

POST/book

Initiate a carrier booking for one or more orders and trigger label generation.

Fulfillment

GET/label

Retrieve a URL to the shipping label for a booked order.

Tracking

GET/track

Pull tracking events, proof of delivery, and estimated delivery dates for a shipment.

Use Cases

Automate the quote-to-label fulfillment flow

- Request multi-carrier quotes at checkout and select the optimal service level by price and ETA - Create orders, book carriers, and pull label URLs without manual portal steps - Consolidate and group orders for efficient batch dispatch

Sync shipment tracking into customer and ops tools

- Stream tracking events and proof of delivery into CX, support, and notification systems - Reconcile pull-based /track data with push-based webhook updates for a single status source - Surface estimated delivery dates and exceptions to retention and ops dashboards

Power returns and post-purchase workflows

- Trigger returns requests and notifications through the returns portal API - Feed return status into refund, restock, and customer-communication flows - Track return shipments alongside outbound parcels for unified reporting

Manage multi-store merchant configuration

- Query and update merchant settings, operating hours, and carrier preferences across stores - Register and rotate webhooks programmatically for real-time status updates - Route calls to the correct store API key for multi-region operations

Technical Specifications

Authentication

Store-specific Shippit API key handled in a managed, encrypted session

Connectivity

Authenticated REST calls against the Shippit v3 API plus the separate NowGo fleet surface

Response format

Normalized JSON across orders, quotes, shipments, labels, tracking, and returns objects

Rate limits

Adaptive throttling tuned to your store volume to stay within Shippit and carrier-side limits

Session management

Automatic key management, rotation, and per-store routing across regions

Data freshness

Near real-time order and tracking pulls with optional scheduled batch syncs

Security

Encrypted credential vault, scoped access, SOC 2-aligned controls, and audit logging

Webhooks

Event callbacks for order status changes, tracking updates, and proof of delivery

Latency

Sub-second reads on cached entities; multi-second writes when booking carriers and generating labels

Throughput

Horizontally scaled workers sized to high-volume ecommerce dispatch across stores

Reliability

Retry, backoff, and idempotency keys for order creation, bookings, and label requests

Adaptation

Continuous monitoring of Shippit API releases and carrier behavior changes for drift-free operation

Frequently asked questions

Shippit uses API key authentication, with each store issued its own unique key after payment details are added. Supergood securely manages these store-specific keys and routes each call to the correct store and region.

Yes. Supergood orchestrates the full quote → order → book → label → track flow over Shippit's v3 APIs and normalizes the responses, so you can integrate the entire fulfillment lifecycle through one consistent surface.

Both are supported. Shippit offers pull-based tracking through the /track endpoint and push-based updates via webhooks. Supergood reconciles the two so you get a single, deduplicated source of truth for shipment status.

Yes. NowGo dispatch, routing, and driver data live on a separate API surface, and Supergood stitches it together with the multi-carrier shipping data so own-fleet and carrier shipments sit alongside each other.

Yes. Supergood manages per-store API keys for multi-store and multi-region setups, and exposes the returns portal API for request and notification workflows alongside outbound shipments.

Ready to get a real API?