Stocky API

Shopify Discussion
, ,
1

Hi everyone,

I was wondering if this Stocky’s API is still functionnal : API documentation

I appreciate everything is going down on 31st of August but keen to know if we can still use that to extract PO’s until then ?

Thanks a lot

2

Hi @Pipokx .

Hope you are doing great.
The docs page is still up API structure is still listed.

To be sure it works, test the purchase orders.json endpoint directly.

For certain until Aug 31, check with Shopify support.

3

Hey @SectionKit team, thanks a lot :slight_smile:

4

Hello there @Pipokx
The Stocky API is still live until the deprecation date, so you can use this method for extracting POs for now. It’s better to keep your calls for read, rather than build another dependency on it, the way stability probably won’t improve. A good work around is to schedule exports of your purchase orders using Stocky reports, or manual exports using the Shopify admin alongside the API so that you have continuity, your endpoint could fail any time before August 31.

5

Agreed the above API should be good at least until Aug 31.

If it helps - with Stocky going away, and our own users asking us for a robust way to handle POs and light inventory management / reordering with Shopify; we decided to build our own solution, but for free - and it has a one click migration to pull all your POs in from Stocky, if helpful!

Check it out at Stockroom - Stockroom ‑ Purchase Orders - Unlimited purchase orders, receiving & sync with QuickBooks | Shopify App Store - we’re making it completely free for everyone!

We think Shopify merchants deserve a robust, stable and long term way to handle Purchase Orders (and the re-ordering/receiving processes that come with them) in a way that fits their business, and not at an additional cost.

6

It seems Shopify will be releasing API’s for native purchase orders in the coming weeks (or months).

7

Been digging into this exact problem, so sharing what I’ve found in case it helps anyone here.

Stocky has an official read-only API — docs are at API documentation , and you can generate your key inside Stocky under Preferences → API. Auth is just two headers (Store-Name: yourstore.myshopify.com and Authorization: API KEY=yourkey), and it returns JSON for: purchase orders (with full line items), suppliers, stock adjustments, and tax types.

A few gotchas from actually working with it, since the main docs page tells you almost nothing:

  • The real documentation is on the per-resource pages — e.g. stocky.shopifyapps.com/api/docs/v2/purchase_orders/index.html — each has a full example JSON response.
  • Pagination is since_id + limit, but purchase_orders pages backwards (since_id = “give me IDs less than this”, newest first) while suppliers/adjustments/tax_types page forwards (“greater than”). If your script passes since_id=0 to purchase_orders you’ll get zero results and think you have no POs.
  • Purchase orders have a status filter (draft, confirmed, archived, unarchived) — worth pulling explicitly so you don’t silently miss archived or draft POs.

Two things worth knowing before Aug 31:

  1. Your supplier records are recoverable. The help doc says suppliers can’t be exported, but the API has a working suppliers endpoint. If you’ve built up years of supplier details, they’re not stranded.
  2. Stocktakes and transfers are NOT in the API. For those, the per-stocktake CSV buttons and the Reports dropdown are the only path — do those manually before the deadline, they’re gone after.

If you’re comfortable writing a small script, the above is everything you need to pull your data yourself.

If you’re not: I’m a developer and I’ve built a one-click version — paste your store name + API key, it pulls everything and hands you a ZIP of CSVs and JSON that you keep locally. No new subscription, no migrating into another inventory app. Just your data, archived, before it disappears.

Because Stocky is delisted I can’t install it on a dev store to test, so I’m looking for 2–3 merchants willing to run it on their real data first — free full archive for testers, and I’d genuinely value hearing what else you’d want included. DM me if you want to help me test it.