Skip to main content
The fastest way to get started with Shippo is a single API account. For many developers, that’s exactly the right setup. But if you’re building a product where multiple businesses or merchants ship through your integration, the path you choose here affects how billing, carrier management, and reporting work at scale. This guide walks you through the decision.
Carriers including USPS, UPS, and Canada Post require e-commerce marketplaces to use separate Managed Shippo accounts for each merchant. If you run a marketplace, a Platform Account is not optional.

Start here: what are you building?

Answer one question before you write your first API call.

My own business ships packages


You’re a single company sending your own shipments and you are the shipper of record.Use our quickstart guide →

I'm building a platform for other businesses to ship

You’re a marketplace, WMS, e-commerce platform, or other app where merchants or customers ship through your product.See your account model options below.

If you’re a platform: choose your account model

Platforms have two options depending on who owns the billing relationship with each merchant.

White label (Platform Accounts)

You own the billing relationship. Shippo is invisible to your merchants. You create and manage a headless Managed Account for each merchant via the API. When making API calls on behalf of a merchant, include their account ID in the request header: SHIPPO-ACCOUNT-ID: <id>
  • Billing: You collect and manage with your shippers
  • Branding: Fully yours, Shippo invisible
  • Merchant login: None required
  • Best for: Marketplaces, SaaS platforms, 3PLs
Platform Accounts documentation →

Gray label (OAuth)

Your merchants create their own Shippo accounts and connect via OAuth. Shippo bills them directly. You receive an OAuth token and make API calls on their behalf. Setup requires a contact email and callback URL from you. Shippo provides an OAuth ID and secret. Merchants authorize your platform through the Shippo OAuth flow.
  • Billing: Shippo handles directly
  • Branding: Co-branded (Shippo visible)
  • Merchant login: Merchants create Shippo accounts
  • Best for: WMS, IMS, and tools where merchants want their own Shippo relationship
OAuth documentation →

Then: how do you want to build the UI?

This decision is separate from your account model and applies to both white label and gray label integrations.

Build native UI

Call the Shippo API directly and build your own interface. Most flexible, most work. You own the entire experience.

Shipping Elements

Embed Shippo’s pre-built shipping widget using a JavaScript SDK. Include one script tag, call init() to authenticate, and render it into your page. Shippo maintains and updates it. Supports both white and gray label.

How the account structures compare

Each model has a different relationship between your platform, Shippo, and your merchants.
Direct APIWhite LabelGray Label (OAuth)
Account structureAll shipments on your single Shippo accountPlatform account with one headless Managed Account per merchantEach merchant connects their own Shippo account via OAuth token
Recommended for platformsNoYesYes

Quick comparison

Direct APIWhite LabelGray Label (OAuth)
Who owns billingYouYouShippo (billed per merchant)
Merchant Shippo accountNone (your account)Managed, headless, invisibleMerchant’s own account
Shippo visible to merchantsN/ANoYes (co-branded)
Per-merchant carrier accountsNo — sharedYesYes
Per-merchant reportingNo — commingledYesYes
Merchant manages Shippo loginNoNoYes
Setup complexityLowMedium — request Platform AccountMedium — set up OAuth credentials
To set up a Platform Account (white label) or OAuth credentials (gray label), contact Shippo or reach out to your account team. Both require a brief setup step before you can begin building.