Skip to main content
All featuresDevelopers

Sandbox

Build and test your integration against a separate copy of the API with its own accounts and keys. Billing runs in Stripe test mode and carrier calls go to each carrier's test environment, so no money moves and labels come back watermarked. A badge in the toolbar shows whenever you're in the sandbox. Build full test pipelines before deploying to any production facing application.

How ShipGenius differs

UPS, USPS and FedEx work in the sandbox without registering anything, using ShipGenius house test accounts. Addresses, dimensions and services are still checked by the carrier, so a rejection in the sandbox matches what production would do. These are live carrier sandbox labels directly from their API's, this is the best simulation you'll find for this.

How it works

The sandbox is a separate deployment of the ShipGenius API at sandbox.lite.shipgeni.us. It has its own accounts, data and API keys, and runs the same schema, validation and permission checks as production. A sandbox key only works against the sandbox endpoint. A badge in the toolbar shows whenever you're signed in to the sandbox.

What you can test

  • Billing: Stripe runs in test mode, so you add credits with Stripe's test cards and bank details and no money moves. Use the declining card to test a failed purchase.
  • Carriers: every carrier call goes to that carrier's test environment. UPS, USPS and FedEx work without registering anything, using ShipGenius house test accounts. DHL, Passport, UniUni and Pitney Bowes need your own test credentials.
  • Labels: each label comes from a real carrier call and carries a watermark, so it can't be used to ship.
  • Validation: addresses, dimensions and service availability are checked by the carrier, the same as production.

What's different

  • Rates are placeholder numbers from the carrier test environments.
  • Rate limits are tighter.
  • Marketplace integrations and two-factor authentication aren't available.
  • Data is temporary and can be wiped.

Moving to production

Switch the endpoint host and use a key from an app created on your production account. Operations, field names and error codes stay the same.

Read more in API keys and connected apps.