Moving from Extensiv 3PL WMS to ShipHero: API endpoint & setup questions

Getting Started
1

I’m coming from Extensiv 3PL Warehouse Manager and am comfortable with their REST endpoints. This client wants the same integration behavior they had in Extensiv, but now against ShipHero. I’m new to ShipHero’s API style and want to confirm the right approach before giving the client a final mapping.

What the client previously used in Extensiv

  1. Create orders:
    POST https://secure-wms.com/orders

  2. Find inbound “receivers” by tracking/reference number:
    GET https://secure-wms.com/inventory/receivers/
    (filtered by ReferenceNum containing TrackingNumber)

  3. Get file/image summaries for a receiver:
    GET https://secure-wms.com/inventory/receivers/:receiver_id/filesummaries/

  4. Download an attached image/file:
    GET https://secure-wms.com/inventory/receivers/:receiver_id/files/:filename

What I need to confirm for ShipHero

  • Equivalent order create flow

  • Equivalent inbound/receiver lookup flow

  • How to access attachments/images for inbound receipts/POs (if supported)

To summarize, the customer wants to be able to create orders, search purchase orders (POs) using a reference field, and retrieve any images attached to both POs and orders. I’m completely new to ShipHero’s API, and I’m hoping to get a strong head start so I can support our clients and help ensure a smooth transition to the new software.

2

Hello,

Welcome to Shiphero and the community! Switching from a REST API to GraphQL may take some getting used to, but I am confident you can replicate the workflow in our API.

At a top level you can find our documentation at https://developer.shiphero.com/ and a full schema of our API at ShipHero GraphQL API.

The relevant calls for your needs can be found at:

and

For files attached to POs you’ll want to look at the attachments connection in the purchase order body. This will contain hyperlinks to files that can be used for download.

The only discrepancy between these workflows would be the availability of tacking number as a filter on the purchase order query. You may instead need to use some combination of PO number and date form/date to.

Thanks

4

The only discrepancy between these workflows would be the availability of tacking number as a filter on the purchase order query. You may instead need to use some combination of PO number and date form/date to.

Our workaround has been using the PO name as the tracking number and filtering it that way. I assume this would also work for Shiphero?