Picked developer docs

Connect your ERP, webshop or own tooling to your Picked warehouse through the Picked API.

Where to start

• Getting started: create an API token and make your first call.
• Authentication & abilities: which token can call which endpoint.
• API reference: every endpoint, its parameters and its responses.

Guides

• Errors: every error code, and whether to retry.
• Rate limits: how many calls you can make, and what to do past the limit.
• Idempotency: which calls are safe to send again.
• Paging through stock changes: polling stock changes without missing one.
• Dry runs: trying a write without writing anything.
• Versioning & deprecation: what can change in v1, and what can't.
• Changelog: every change to the API.

Recipes

• You may not need the API: the shops, ERPs, carriers and spreadsheets Picked connects to by itself.
• Push orders from your ERP or webshop: send orders to the warehouse.
• Keep your webshop's stock in sync: publish what you can sell.
• Announce an incoming delivery: tell the warehouse what's coming and follow the receiving.
• Resume a process from an outside system: let a process wait for a signal from your system.
• Start a process run from an outside system: put a piece of work on the floor, with its starting variables.
• Let your system decide a step: a step calls your system and waits for its answer.
• Connect an AI agent over MCP: let your own agent build processes.

How the API works

The API lives at https://picked.nl/api/v1. Every request carries a bearer token that belongs to one workspace, and a token can only do what its abilities allow.

Answers carry HAL-style _links, each an href under the host. A resource you can read on its own links itself (_links.self); a page links itself and, while there are, the pages either side (_links.next, _links.prev); a cursor feed links its next read while more is waiting. A call that makes something answers 201 with a Location header where to read it. Follow the links rather than building paths yourself.