Shipping API

Introducing API Versioning and Test Mode

Thu 27 Oct 2016
By Shippo Engineering

shippo version 2016-10-25

We are excited to introduce the next version of Shippo API.

After printing millions of labels and having thousands of developers integrating our API, we’ve  taken all the feedback and decided to improve the API by rolling out versioning.

We will continue to improve and release new features for all versions of our API as we have done in the past. However, we’ve been restricted with old functionalities, being careful that we don’t break any existing integrations.

Now, with API versioning, we can systematically release updates that may be backwards-incompatible and let developers choose if they’d like to upgrade. We hope this improves the developer experience for all of our customers. 

Current Shippo users can continuing using Shippo as is, and test their code under a different API version before upgrading. 

Simply set Shippo-API-Version in the header with the version you are testing.

curl https://api.goshippo.com/shipments/  \
    -H "Authorization: ShippoToken <PRIVATE_TOKEN>" \
    -H "Shippo-API-Version: YYYY-MM-DD" \
    -d '{ ... }'
# now this API request uses the API version "YYYY-MM-DD"

Learn more about API versioning and check out our changelog for details about the latest versions. 

Test Mode for Version 2016-10-25

With this new version, we’ve introduced Test Tokens for the Shippo API. You’ll be able to set your account to full test mode, and use the API without being worried about being charged. 

Test Tokens are simple to use. Just insert it in place of your Live Token, and off you go. From creating Shipments all the way to generating test labels, you’ll be able to try out the Shippo API end-to-end. 

Review Test Mode documentation to learn more.

Next post

Oct 31, 2016
Stripe Connect for Shipping

Previous posts

Oct 13, 2016
See you in Boston at APIStrat

Oct 10, 2016
Snapfulfil Partners with Shippo

Sign up for the Shippo Blog

Receive emails with news and announcements we post on this blog.