Reference · built on requestConnectorShipping & logistics

ShipHero

Orders, shipments, inventory, purchase orders, returns, and event webhooks from the ShipHero GraphQL API.

Request accessPricing ↗

About

ShipHero is a warehouse management system used by brands and 3PLs to pick, pack, and ship. Its public API is a single GraphQL endpoint. Queries return orders with their fulfillment status, shipments with packages and tracking, warehouse products with on-hand quantity, inventory changes by SKU, purchase orders with received quantities, returns, totes, cycle counts, and license plate numbers. Mutations create orders, record shipments made elsewhere, add or remove inventory, open and close purchase orders, and create returns with exchange items. Webhooks push Shipment Update, Inventory Update, Order Canceled, PO Update, Return Update, and others to your endpoint, each signed.

Through Fibric, an operator reads shipments and stock across warehouses and proposes the reorder, the receipt, or the return status change for your approval.

This is a reference listing. It documents what Fibric would read from ShipHero and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • orders and order queries with fulfillment_status, filtered by shop_name, plus order_history for what changed
  • shipments and shipment queries with packages, tracking numbers, and carriers, and packs_per_day and picks_per_day by date range
  • warehouse_products per warehouse, item_locations per bin, and inventory_changes by SKU
  • purchase_orders with line items, quantity_received, quantity_rejected, and sell_ahead per SKU
  • Returns with line items, return reasons, condition, and a status of Pending, Warehouse Complete, or Complete
  • Webhooks: Shipment Update, Inventory Update, Inventory Change, Order Canceled, Order Allocated, Order Backorder, PO Update, Return Update, Tote Complete, and Shipment ASN
  • Cycle counts, totes, kits, lots, and license_plate_numbers

Proposed actions

  • Target capability: propose an order through order_create, or an update through order_update and order_update_fulfillment_status
  • Target capability: propose recording a shipment made outside ShipHero through shipment_create with labels, followed by inventory_remove
  • Target capability: propose a purchase order through purchase_order_create, its receipts through purchase_order_update, and closure through purchase_order_close
  • Target capability: propose a return through return_create with exchange_items, and its status through return_update_status
  • Target capability: propose inventory_add for stock received outside a purchase order

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Reorder before the bin runs dry

    Read warehouse_products and inventory_changes by SKU, compare with open purchase_orders, and propose the purchase_order_create with vendor, warehouse, and quantities.

    With Reorder Point, Purchase Order Draft

  • Chase the purchase order that has not landed

    Follow PO Update webhooks and quantity_received against the po_date. When a line is short or late, propose the vendor follow-up and the close decision.

    With PO Chase, Inbound Delay

  • Move a return through the warehouse

    Follow Return Update and return_receive_line_item, then propose the return_update_status change to Warehouse Complete or Complete. The refund fires only on Complete, after approval.

    With Return Restock, Returns Triage

  • Keep the storefront honest about stock

    Read Inventory Update and Order Allocated webhooks and propose the channel quantity change when allocation leaves a SKU short.

    With Oversell Watch

Requirements

  • A ShipHero account and a Third-Party Developer user created from the dashboard users page for the integration
  • Queries sized to the credit budget: 4,004 credits at start, 60 restored per second, no single operation above 4,004
  • An asynchronous webhook endpoint that answers within 10 seconds, 20 for Generate Label
  • The shared_signature_secret saved at webhook creation; it is shown once
Authentication
A Bearer access token from POST https://public-api.shiphero.com/auth/token with a username and password; tokens expire every 28 days and are renewed through /auth/refresh without re-entering credentials.

Limits

  • Throttling is by complexity credits, not requests; every response reports request_id and complexity, and analyze: true prices a query without running it
  • Connection fields page at most 100 records per call by default
  • Webhooks retry 5 times per trigger and are disabled automatically once marked UNHEALTHY
  • A Complete return status triggers the refund, so status changes are proposed, never automatic

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request ShipHero ↗

Questions and answers

How is the ShipHero API throttled?
By complexity credits. An account starts with 4,004 credits, 60 are restored every second, and no operation may exceed 4,004. Every response returns request_id and complexity. Send analyze: true to learn a query's cost without executing it. Connection fields default to a maximum of 100 records.
How are webhooks registered and checked?
Call the webhook_create mutation with name, url, and shop_name; the name is the exact webhook type, such as Inventory Update. ShipHero returns a shared_signature_secret once. Each delivery carries x-shiphero-hmac-sha256 and X-Shiphero-Message-ID headers and expects a JSON body with code 200 and Status Success in reply.
How long does an access token last?
28 days; the token response reports expires_in of 2419200 seconds. Renew it at /auth/refresh with the refresh token. For integrations, create a Third-Party Developer user from the dashboard so the credentials are separate from a person's login.
Ask about ShipHero

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with ShipHero through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy