Integrating Linnworks
Auth: OAuth 2.0 · Partner program: required · Setup time: about 25 minutes · Last verified: 2026-05-23
Linnworks is a UK-based multichannel order + inventory management platform. The adapter wraps the Linnworks.net API and surfaces stock items, locations, stock levels, suppliers, and stock movements into the canonical inventory schema.
Auth model
Section titled “Auth model”- OAuth 2.0 Client Credentials grant for channel integrations: POST to
https://api.linnworks.net/api/Auth/AuthorizeByApplicationwithapplicationId,applicationSecret, and a per-installtoken. - Application install flow (Linnworks’ equivalent of “user authorization”): the merchant clicks an install link in the Linnworks app store, which produces a static
tokenthat the integration then exchanges viaAuthorizeByApplicationfor anAuthorizationtoken. - The returned
Tokenis the bearer used in theAuthorizationheader for every API call; the response also includesServer(the per-install API host such ashttps://eu-ext.linnworks.net).
Prerequisites
Section titled “Prerequisites”- A Linnworks account at linnworks.com.
- A registered System Integration application in the Linnworks Developer Portal (developer.linnworks.com). Note the Application ID, Application Secret, and configure the install URL + scope manifest.
- To publish on the Linnworks App Store you must enrol in the Linnworks partner programme and pass app review.
Configure in admin
Section titled “Configure in admin”- Open
/platformsin the admin UI, filter to Inventory, click Linnworks. - Fill Configure:
clientId— your Linnworks Application ID.clientSecret— your Linnworks Application Secret.redirectUri—${PUBLIC_BASE_URL}/auth/inventory/linnworks/callback(used as the install completion URL).
- Enable the adapter. On each install the adapter calls
AuthorizeByApplicationwith the installtokenand stores the returnedToken+Server.
Required scopes
Section titled “Required scopes”Scopes are declared in the application manifest at registration time and granted during install — Linnworks issues a space-delimited list back at auth time. Request scopes covering Inventory (Inventory.View, Inventory.Edit), Stock (Stock.View, Stock.Edit), Locations, and Suppliers.
Webhooks
Section titled “Webhooks”Linnworks does not provide HMAC-signed webhooks at the API level. Real-time data is delivered via the Channel Integration push endpoints you implement on your side (Linnworks calls you when an order or inventory change occurs and authenticates by sending the OAuth bearer token issued at install time). The adapter exposes endpoints to receive these pushes and validates the inbound token against the stored install record.
For inventory-only sync, the adapter falls back to polling Stock/GetStockItemsFull and Stock/GetItemChangesHistory on a configurable cadence.
Quirks worth knowing
Section titled “Quirks worth knowing”- Per-install API host. The
Serverreturned at install time is sticky for the lifetime of that install — always use it instead ofapi.linnworks.netfor data calls. - Token rotation. Tokens are long-lived but can be revoked from the merchant’s app management UI; on a 401 re-run
AuthorizeByApplicationwith the original install token. - Channel push, not webhooks. Real-time delivery is push from Linnworks to your channel endpoints; subscribe carefully.
- EU vs US tenancy. Linnworks runs separate clusters; the
Servervalue tells you which one.
References
Section titled “References”opensteward.dev ·Plans and free license ·Terms ·Privacy ·support@opensteward.dev
© 2026 Falco Consulting AB. Built from open-steward/opensteward@a3961d8. This site sets no cookies, runs no analytics and loads nothing from other sites, except platform logos from Brandfetch on the Platforms page.