What we do
Tools
Industries
Department
How we workLet's talk →
Home/SkuVault/SkuVault API
SkuVault Core

The SkuVault API Allows Some Calls 200 a Minute and Others Five. Plan the Sync Around That.

SkuVault is now SkuVault Core, part of Linnworks, and its API still lives at app.skuvault.com. Every call is a POST with a JSON body, your two tokens ride inside that body, and each endpoint carries its own throttle tier. The token call allows 200 a minute. The big catalog and inventory reads you'll lean on allow five.

SkuVault API, the short version

Base: https://app.skuvault.com/api/, grouped by area, for example /api/products/getProducts or /api/sales/syncOnlineSale. Everything is a POST with Content-Type: application/json.

Tokens: POST a SkuVault login's email and password to /api/gettokens. You get a TenantToken (one per account) and a UserToken (one per user). Both go in the JSON body of every later call, not in a header.

Throttles: each endpoint is tagged Very Light (200 calls a minute), Light (20), Moderate (10), Heavy (5) or Severe (1). Go over and you get a 429, with X-RateLimit-Reset giving the wait in milliseconds.

Paging: the big list calls take PageNumber starting at 0 and a PageSize between 1,000 and 10,000.

SkuVault endpoints by job, with the tier that limits each one

Endpoint What it does for you Tier, and the catch
/api/gettokens Swaps a SkuVault login for the tenant and user tokens. Very Light. A disabled user gets no tokens back, so don't build on a staff member's own login.
/api/products/getProducts Pulls the catalog, up to 10,000 products a page. Heavy, five a minute. Pull it on a slow schedule and let other jobs read your copy.
/api/inventory/getInventoryByLocation Quantity and reserved stock by SKU, broken out by warehouse and location. Heavy. Right for a scheduled snapshot, wrong for a check on every order.
/api/inventory/setItemQuantity Sets the quantity for a SKU at one warehouse location, using a WarehouseId from getWarehouses. Moderate, ten a minute. It writes the number you send. It doesn't add or subtract.
/api/sales/syncOnlineSale Creates a sale, or updates it when that OrderId already exists. /syncOnlineSales does the same in bulk. Moderate. Use the bulk call once orders arrive faster than a trickle.
/api/sales/getSalesByDate Sales in a date range, matched on order date or last-modified date. Heavy, and the range can be seven days at most.

SkuVault integrations that stall on 429s or overwrite good counts

Every job re-pulls the whole catalog

How you'll know: 429s every few minutes, because getProducts is Heavy and three separate jobs are calling it.

Fix: Pull the catalog once on a schedule, cache it, and point every other job at the cache. Space calls to each tier's per-minute limit rather than waiting for the 429.

Quantity math done outside SkuVault, then written back

How you'll know: A sync reads a bin's count, adds a received quantity and writes the total with setItemQuantity, while a picker pulled from that bin in between. The bin is now off by whatever was picked.

Fix: setItemQuantity writes an absolute number. Use it only for locations where your system genuinely owns the count, such as stock held by an outside warehouse whose figure you trust.

Backfilling a month of sales in one request

How you'll know: getSalesByDate rejects the range, or a long backfill crawls for hours.

Fix: Step through seven-day windows, set DateField to last-modified when you only want changes, and space the calls for the Heavy tier.

Tokens fetched with one employee's login

How you'll know: Someone leaves, their SkuVault user gets disabled, and the integration can no longer fetch its tokens.

Fix: Create a SkuVault user just for the integration, fetch its tokens once, and store them as secrets outside the code.

What a SkuVault API build becomes inside a warehouse

The worthwhile builds sit between SkuVault Core and systems its prebuilt integrations don't cover the way you need. Stock value and cost of goods posted to accounting the way your finance team tracks landed cost, not a generic mapping. A morning view of stock levels and sales velocity your ops lead opens without exporting a report. Orders from a wholesale portal or a channel with no ready connector, sent in through syncOnlineSale so a resend updates the order instead of duplicating it.

n-frames writes these against the throttle tiers from the first line of code: Heavy reads on a schedule, writes batched through the bulk calls, and a queue that waits out X-RateLimit-Reset instead of dropping work.

SkuVault API questions from the people writing the code

Does SkuVault have a public API?

Yes. SkuVault Core, now part of Linnworks, documents its API at dev.skuvault.com. It covers products, inventory by warehouse and location, sales and more, with tokens you fetch using a SkuVault login.

Do I need a developer to use the SkuVault API?

Yes. There's no point-and-click builder on top of it: someone has to write the code that fetches tokens, respects each call's throttle tier and recovers from 429s. When nobody in-house has the time, n-frames builds that integration for you.

Can SkuVault's API connect to Shopify or WooCommerce directly?

The API doesn't connect to anything on its own. Your code calls SkuVault on one side and the store's API on the other. For a standard store, look at SkuVault Core's own channel integrations first. The API earns its place when the store setup doesn't fit them, like a wholesale storefront with its own order rules.

Is SkuVault's API the same connection used for its ShipStation integration?

Treat them as separate. The ShipStation integration is a prebuilt connection you switch on in SkuVault Core, and the API is general access for your own code. You can run both, as long as they aren't writing the same quantities or sales.

What happens when I hit the SkuVault rate limit?

You get a 429 with three headers: X-RateLimit-Limit, X-RateLimit-Remaining, and X-RateLimit-Reset, the wait in milliseconds. Hold that call until the reset has passed, then carry on.

Let's talk

Tell us the one thing your team does manually that eats up time. We read every message and reply within a day.