What you need
A ShipStation V1 API key and secret. Generate them from your ShipStation API settings. The Get keys link on the Egentify card takes you straight to ShipStation’s instructions.Connect ShipStation
1
Turn ShipStation on
In your Egentify dashboard, go to Store Settings > Integrations and toggle ShipStation on. The credential fields appear once the toggle is on.
2
Enter and save your credentials
Paste your values into API Key and API Secret, then save. Both are stored encrypted and show a Configured pill once saved.
3
Verify to map your store
Click Verify channel. The button stays disabled until your keys are saved, because Egentify uses them to fetch your store list.
Mapping your ShipStation store
One ShipStation account can hold orders from several storefronts, which ShipStation calls stores. Egentify needs to know which one holds this store’s orders, otherwise a lookup for order#1001 could land on a different storefront entirely.
When you verify, Egentify fetches your active stores, tries to match one by comparing its configured URL to your store address, then confirms it can actually find one of your five most recent orders there. If the automatic match is ambiguous, the picker opens so you can choose.
A correct mapping matters more than it looks. A wrong store returns “order not found”, which is indistinguishable from “order not shipped”, and that is the exact mistake that would let a shipped order be cancelled and refunded.
What is specific to ShipStation
Orders handed to a supplier cannot have their address changed. Once ShipStation marks an order as delegated or pending fulfillment, Egentify will decline an address change on it. Split shipments. If any package on an order has shipped, Egentify treats the whole order as shipped and blocks the cancellation. Confirm this behaves as you expect against your own data before relying on it, since how ShipStation labels sibling packages on a split order varies. Rate limits. ShipStation caps API traffic at roughly 40 requests per minute, so cancellation dialogs can feel slow against a busy account. This is normal and not a fault in the connection.When something goes wrong
“ShipStation rejected those credentials.” Re-enter your API key and secret. Keys generated for the V2 API will not work here. “Couldn’t auto-match, choose your store below.” The store’s configured URL in ShipStation does not match your store address. Pick the right one from the list. “Mapped to X, but no recent order was found there.” Either the store is wrong, or your orders have not synced into ShipStation yet. A brand new store with no orders lands here too. Cancellations stay protected until this clears. “Couldn’t reach ShipStation right now.” A temporary outage. Try again in a moment.Rotating your API keys, changing the mapped store, or changing your project’s store URL all clear the verified status. Click Re-verify afterwards, or cancellations will stay blocked.