Integrate iPaaS.com with Linnworks to enable seamless data synchronization for orders, products, inventory, and shipments.
How to Connect
Prerequisites
Before configuring the integration in iPaaS.com, set up API access in your Linnworks account:
Register (or obtain) a Linnworks Application so the integration can authenticate on your behalf, and generate an installation token for it. Linnworks issues an Application Id, Application Secret, and a token that together authorize API access. See the Linnworks Developer documentation at https://apidocs.linnworks.net for how to create an application and obtain these values.
Ensure the Linnworks account has permission to read orders and to manage products, inventory, and shipments, so both inbound and outbound synchronization can operate.
Configuration Details
You will need the following values to connect:
API Url: The base URL of the Linnworks API your account uses. This is region-specific — for example, https://eu-ext.linnworks.net/api for EU-hosted accounts. iPaaS.com uses this to send all requests to Linnworks.
Token: The Linnworks installation token that authorizes the integration. This is required.
Application Id: The identifier of your Linnworks application. Optional — if left blank, the integration uses its built-in application registration.
Application Secret: The secret paired with your Linnworks application. Optional — if left blank, the integration uses its built-in application registration.
Configure Subscription Settings
In your iPaaS.com subscription, open the Linnworks subscription settings and complete the fields below.
Field | Description | Required | Example |
API Url | The region-specific base URL used for all Linnworks API requests. | Yes | |
Token | The Linnworks installation token that authorizes the integration. | Yes | (your Linnworks token) |
Application Id | Your Linnworks application identifier. If left blank, the integration's built-in application is used. | No | (your application id) |
Application Secret | Your Linnworks application secret. If left blank, the integration's built-in application is used. | No | (your application secret) |
Poll Orders By Locations | A comma-separated list of Linnworks fulfilment location names. When set, only orders from those locations are polled; when blank, orders from all locations are polled. | No | Main, North Warehouse |
Concurrent Batch Executions | Limits how many batches the integration processes at once during high-volume transfers. Pre-populated by the integration. | Yes | 10 |
Authentication Methods
The integration authenticates to Linnworks using Linnworks application authentication:
Enter your API Url and Token in the subscription settings (and your Application Id and Application Secret if you are using your own Linnworks application).
Using the Application Id, Application Secret, and Token, iPaaS.com obtains a Linnworks access token and uses it to authorize API requests.
The access token is cached and refreshed automatically when it expires, so no manual token renewal is required during normal operation.
If your Token is revoked or regenerated in Linnworks, update the Token value in the subscription settings so the integration can continue to authenticate.
Initialization Support
Currently, initialization (bulk historical import on first connect) is not supported for Linnworks in iPaaS.com. Data synchronization is driven by the integration's order polling schedule, by the outbound triggers you enable, and by Manual Sync, all configured during the integration process.
Throttling
The integration's throttle and concurrency fields are pre-populated with values suited to Linnworks and can be adjusted for your volume — reduce them if you encounter rate-limit errors. The default values are an API throttle limit of 500 calls per 60 seconds (in each direction), 10 concurrent connections, and 10 concurrent batch executions. For details on how these fields behave, see the Subscription Configuration – Edit article in the iPaaS.com Help Center.