canonical: https://jentic.com/apis/picqer.com/picqer # Picqer API Jentic publishes the only available OpenAPI specification for Picqer API, keeping it validated and agent-ready. Picqer API provides warehouse management capabilities including product catalog operations, order processing, customer records, picklist generation, and multi-warehouse coordination. The API enables fulfillment workflows from order intake through pick-pack-ship with real-time inventory tracking across multiple warehouse locations. ## For AI agents Manage warehouse inventory, process fulfillment orders, generate picklists, and track stock levels across multiple warehouse locations. ## Scope Does not handle shipping label generation, carrier rate comparison, or storefront management - use for warehouse inventory and order fulfillment only. ## Capabilities - Track product stock levels and locations across multiple warehouses - Generate and manage picklists for order fulfillment workflows - Process incoming orders and route them to appropriate warehouse locations - Maintain customer records with shipping and billing details - Configure webhooks to receive real-time inventory and order notifications - Coordinate multi-warehouse stock transfers and allocation ## Use cases ### Multi-Warehouse Inventory Tracking Monitor stock levels across multiple warehouse locations in real time. Picqer API returns per-warehouse product quantities so teams can identify where stock is available, plan transfers between locations, and prevent overselling. Integration enables automated low-stock alerts and reorder triggers. Example prompt: Retrieve the current stock level for product ID 12345 across all warehouses and identify which location has the highest quantity ### Order Fulfillment Automation Automate the pick-pack-ship workflow by creating orders, generating picklists, and tracking fulfillment progress. The Picqer API handles order routing to the correct warehouse and picklist generation based on product location, reducing manual intervention in the fulfillment pipeline. Example prompt: Create a new order with 3 line items and generate a picklist for warehouse ID 1 ### E-Commerce Order Sync Synchronize orders from e-commerce platforms into Picqer for centralized fulfillment. The API accepts order creation with customer details, product references, and shipping requirements, enabling a single fulfillment backend for multiple sales channels. Example prompt: Create a customer record and submit a new order with shipping address and 2 product line items ### AI Agent Warehouse Operations AI agents use the Picqer API through Jentic to automate inventory checks, order creation, and fulfillment status monitoring without manual API configuration. Agents search for warehouse operations by intent, load the operation schema, and execute calls with Jentic handling authentication and rate limiting. Example prompt: Search Jentic for 'check warehouse stock levels', load the Picqer products endpoint schema, and query inventory for all active products ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/products` | List all products with stock levels | | GET | `/products/{idproduct}` | Retrieve a specific product | | GET | `/orders` | List all orders | | GET | `/orders/{idorder}` | Retrieve a specific order | | GET | `/customers` | List all customers | | GET | `/picklists` | List picklists for fulfillment | | GET | `/warehouses` | List all warehouse locations | ## Key resources - **Products** — Create, retrieve, and update product records with stock information - **Orders** — Create and manage fulfillment orders with line items - **Customers** — Manage customer profiles with shipping details - **Picklists** — Generate and track picklists for warehouse picking - **Warehouses** — List and manage warehouse locations - **Webhooks** — Subscribe to real-time event notifications ## Why Jentic - **Setup:** Wiring the Picqer API by hand means setting up its basic auth with your API key as the username, resolving your account subdomain into the host, and coding each stock, order, and picklist lookup yourself. Through Jentic you install once, import Picqer from the API Directory, store the API key once, and your agent calls it. - **Permission scoping:** Picqer puts resource ids in the URL path (`/products/{idproduct}`, `/orders/{idorder}`), so a rule can pin your agent to reading a specific product or order. The operations exposed here are all reads, so you can allow stock and order lookups without granting any write, and you choose which of those reads the agent may call. - **Credential handling:** Your Picqer API key is stored once, encrypted, by your own Jentic One instance and injected at execution time. It never enters the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'check warehouse stock levels' or 'look up an order', and Jentic returns the matching Picqer operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **ShipStation API** — ShipStation handles shipping label generation and carrier rate comparison after Picqer completes picking - **Shopify API** — Shopify manages the storefront and sends orders to Picqer for warehouse fulfillment - **AfterShip API** — AfterShip provides shipment tracking and delivery notifications after orders leave the warehouse ## FAQ ### Why is there no official OpenAPI spec for Picqer API? Picqer does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Picqer API via structured tooling. It is validated against the live API and kept up to date. Get started with Jentic One, the self-hosted execution layer. ### What authentication does the Picqer API use? The Picqer API uses HTTP Basic authentication where your API key is the username and no password is required. Through Jentic, these credentials are stored encrypted in your Jentic One instance and agents receive scoped access without handling raw keys directly. ### Can I track inventory across multiple warehouses with the Picqer API? Yes. The /products endpoint returns stock quantities broken down by warehouse location. You can also use the /warehouses endpoint to list all configured warehouse locations and then query product stock per warehouse. ### How do I generate a picklist through the Picqer API using Jentic? Search Jentic for 'generate picklist for order fulfillment', load the /picklists operation schema, and execute the call with your order IDs. Jentic handles the Basic auth header injection and returns the generated picklist with item locations. ### What are the rate limits for the Picqer API? Picqer applies rate limits per account subdomain. The standard limit is 100 requests per minute. The API returns HTTP 429 when the limit is exceeded, with a Retry-After header indicating when to resume. ### Can I set up webhooks to monitor order and inventory changes? Yes. The /webhooks endpoint lets you register callback URLs for events such as order creation, stock level changes, and picklist completion. Webhooks deliver real-time notifications so agents can react to warehouse events without polling. ### Can I limit what my agent is allowed to do with the Picqer API? Yes. Because you run Jentic One yourself, your own rules decide which Picqer operations and credentials the agent may use. Every operation exposed here is read-only, so you can let the agent look up products, orders, customers, picklists, and warehouses without granting any write access, and you pick which of those reads it may call. Since Picqer puts resource IDs in the URL path, such as `/products/{idproduct}` and `/orders/{idorder}`, you can also pin the agent to a specific product or order.