Integrations · Stock & fulfilment
Picqer API: connect Picqer to your webshop, marketplaces and accounts
I connect Picqer through the Picqer API, with an API key per application and Picqer's webhooks for events in the warehouse. n8n has no built-in Picqer node and no community node was found, so the integration is custom work in n8n, in your own EU environment.
CustomVia the API, custom-built
What you can do with the Picqer API
- Orders from channels without a standard integration into Picqer
- Free stock from Picqer back to webshop and marketplaces
- Shipped orders and shipping costs to your accounts
- Returns from Picqer back to webshop and accounts
- Keep purchase orders and receipts in sync with your ERP
How the integration works
Picqer works with an API key per application (Basic Auth) and requires a User-Agent on every call. Events such as a new order, a closed picklist or a stock change arrive through signed webhooks; the integration checks the signature and processes the message. Picqer allows about 500 calls per minute, so the integration works in batches and watches the headers.
Facts about the Picqer API
Checked on 2 November 2026 against the official documentation. Limits, prices and versions change; the source is listed per row.
| Fact | What the documentation says | Source |
|---|---|---|
| Authentication | API key as the username in Basic Auth, created under Settings, API Keys; a dedicated key per application. A User-Agent header is mandatory. | Picqer: API |
| Key lifetime | No expiry; the key works until it is revoked. | Picqer: API |
| Rate limits | Normally 500 calls per minute per key, depending on load. When exceeded, 429 and the request is ignored; the headers X-RateLimit-Limit and -Remaining show the room. | Picqer: API |
| Webhooks | Yes: orders, picklists, products, purchase orders, receipts, returns and more, with a signature (X-Picqer-Signature). Respond within ten seconds; fifteen attempts in about seventeen hours; after five complete failures in 24 hours the webhook is disabled. | Picqer: Webhooks |
| Test environment | Developers can request a free Picqer test account. | Picqer: API |
| Version | Only /api/v1/ is active; breaking changes come in a new version URL. | Picqer: API |
| Objects | Products and stock, orders, webshop orders, customers, picklists, shipments, purchase orders, receipts, returns, backorders, warehouses and locations. | Picqer: API |
| API cost | Not in the official documentation. | Picqer: API |
| n8n | No built-in node and no community node found; the integration runs through an HTTP step in n8n. | n8n documentation |
What you need on your side
- A Picqer administrator who can create a separate API key for the integration
- One leading stock: Picqer or your ERP, not both
- Unambiguous item codes across all channels
- Access to the webshop, marketplace or accounts on the other side
Where it often goes wrong, and how I prevent it
- Slow webhook receiver: Picqer waits at most ten seconds for a response and disables a webhook after five failures in a day. The integration responds immediately and processes afterwards.
- Overselling: if free stock does not go back to the channels in time, you sell what is not there. Stock changes are passed on straight away.
- Minute limit: above about 500 calls per minute Picqer ignores the request with a 429. The integration spreads the work.
- Item codes: without an unambiguous item code an order does not land. The integration reports which code is missing.
In practice
A Picqer integration is not yet listed as In production with me. The approach is the same as for bol.com and Sendcloud: webhooks as the signal, the API as the source, one leading stock, and a notification when an order or shipment gets stuck.
What it costs
I build a Picqer integration as one scoped process for a fixed price, from €750. Maintenance and monitoring are a monthly fee: n8n management from €250 per month, server management €145 per server. In the free assessment we work out your process. All prices and what is included →
What I do not do
- I do not set up your warehouse in Picqer; I connect to it.
- I do not let two systems lead the stock at the same time.
- I do not trust a webhook blindly; the integration checks the signature and fetches the current data.
Frequently asked questions about the Picqer API
Does n8n have a Picqer node?
No, and no community node was found either. I connect Picqer through the official API with an HTTP step in n8n.
How many calls per minute does Picqer allow?
Normally about 500 per minute per API key; Picqer may adjust that under load. Above that Picqer returns a 429 and ignores the request. The headers show how much room is left.
Can Picqer notify the integration?
Yes, with webhooks for orders, picklists, products, purchase orders, returns and more, with a signature the integration checks. Picqer retries a message fifteen times in about seventeen hours.
Is there a test environment?
Developers can request a free Picqer test account. I build against that before the integration touches your real warehouse.
What if Picqer disables a webhook?
That happens after five complete failures within 24 hours. The integration is notified and re-enables the webhook through the API once the cause is fixed; in the meantime a scheduled check picks up missed orders.
Related integrations
Often connected together
WooCommerce
In productionPass orders, customers and stock on to accounting or CRM.
More about the WooCommerce integration →Shopify
StandardSync orders, products and customers.
More about the Shopify integration →bol.com
In productionFetch orders, report shipments and update stock through the Retailer API.
More about the bol.com integration →Sendcloud
CustomCreate shipping labels and send tracking to the customer.
More about the Sendcloud integration →