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.