ShipHero GraphQL Public API

For developers building solutions and integrations with ShipHero, our API provides access to a wide range of platform data and features. It’s built on GraphQL, as we focus on offering the most flexible and efficient way to consume your data. Different clients have different implementations and needs, so depending on what you’re building, you may need to fetch data with varying levels of detail. GraphQL is a perfect fit for this, giving you the power to decide exactly how much data you want at any time.

Getting Started
Information on how to access the API and how to authenticate
GraphQL Primer
Our API is built on GraphQL, here’s a primer on our implementation
Examples
Some brief examples of queries & mutations
New! Data Exports
Automatic bulk exports of historical ShipHero data, delivered up to four times per day and accessible via the Public API. Paid add-on.

Latest Changes

2026 March 5th: Added a ready_to_ship field to the Shipment type, enabling customers to calculate fulfillment time metrics (time from ready-to-ship until shipped).

2026 March 4th: Added Inbound Shipments queries and mutations to the Public API. You can now create, update, list, and query inbound shipments, including retrieving images, receiving summaries, and location summaries. New mutations: inbound_shipment_create, inbound_shipment_update. New queries: inbound_shipment, inbound_shipments, inbound_shipment_images, inbound_shipment_summary, inbound_shipment_location_summary.

2026 February 18th: Improved the tote query output type and implemented a totes query to list and search for totes.

2026 February 12th: Added the webhook_update_url mutation to allow changing a webhook’s destination URL without deleting and recreating it.

2026 January 28rd: Added a partner_source_name field to the Order type to help identify orders coming from external partners like TikTok.

2026 January 23rd: Added webhook enable/disable functionality. Webhooks can now be created in a disabled state, enabled, or disabled without deletion. New fields added to webhook responses: enabled, health, created_at, updated_at, and last_enabled_change. Note: Events occurring while a webhook is disabled are discarded and not queued.