canonical: https://jentic.com/apis/swaggerhub.apologistics-gmbh/autostore-controller # Apologistics Gmbh Autostore Controller Autostore API für Ein-/Auslagerung/Kommissionierung. The API exposes 10 endpoints secured with basic authentication. ## For AI agents Programmatically delivers a list of bins with their content information which contains the reques, delivers a list of bins with their content information which contains the reques. Covers 10 operations with basic authentication. ## Scope Does not handle payments, communications, or crm - use for e-commerce only. ## Capabilities - delivers a list of BINs with their content information which contains the reques - releases the requested BIN from the AutoStore via the transfer port - save a BIN to the Autostore which is delivered via the transfer port - Set or unset the compress mode of the AutoStore - returns whether CompressMode is enabled, if so including a list of affected port - retrieves the content information for a specific BIN ## Use cases ### E-Commerce Operations Use the Autostore Controller to perform e commerce operations programmatically. The API provides 10 endpoints covering core functionality including delivers a list of bins with their content information which contains the reques, delivers a list of bins with their content information which contains the reques, releases the requested bin from the autostore via the transfer port. Example prompt: Call GET `/AutoStore/PZN/List/{pzn}` to delivers a list of bins with their content information which contains the reques ### Automated Autostore Management Automate autostore operations by combining multiple Autostore Controller endpoints. Agents can delivers a list of bins with their content information which contains the reques and then releases the requested bin from the autostore via the transfer port in a single workflow. Example prompt: Call GET `/AutoStore/NTIN/List/{ntin}` to delivers a list of bins with their content information which contains the reques, then verify the result ### AI Agent Integration via Jentic AI agents discover and call Autostore Controller endpoints through Jentic without managing credentials directly. An agent searches for the required operation by intent, receives the matching endpoint schema, and executes the call with Jentic-managed authentication. This eliminates the need to read API documentation or handle basic tokens manually. Example prompt: Search Jentic for 'delivers a list of bins with their content information which contains the reques', load the operation schema, and execute with Jentic-managed credentials ## Key endpoints | Method | Path | Description | | --- | --- | --- | | GET | `/AutoStore/PZN/List/{pzn}` | delivers a list of BINs with their content information which contains the reques | | GET | `/AutoStore/NTIN/List/{ntin}` | delivers a list of BINs with their content information which contains the reques | | POST | `/AutoStore/ReleaseAtTransferPort` | releases the requested BIN from the AutoStore via the transfer port | | POST | `/AutoStore/StoreAtTransferPort` | save a BIN to the Autostore which is delivered via the transfer port | | PUT | `/AutoStore/SetCompressMode/{mode}` | Set or unset the compress mode of the AutoStore | | GET | `/AutoStore/CompressModeStatus` | returns whether CompressMode is enabled, if so including a list of affected port | | GET | `/Autostore/BinContent/{bin_id}` | retrieves the content information for a specific BIN | | POST | `/AutoStore/StoreAtCarouselPort` | save a BIN to the Autostore which is delivered via the carousel port | ## Key resources - **Autostore** — Operations for AutoStore - **Autostore** — Operations for Autostore ## Why Jentic - **Setup:** Wiring the Autostore Controller by hand means setting up its HTTP basic auth, tracking the bin and product-code paths, and sequencing the store and release port calls yourself. Through Jentic you install once, import the Autostore Controller from the API Directory, store the basic credentials once, and your agent calls it. - **Permission scoping:** This API puts the bin id in the URL path (`/Autostore/BinContent/{bin_id}`), so a rule can pin your agent to one bin's content and nothing else. You choose the operations it may call, so ones like releasing at a transfer port or changing compress mode are not included unless you add them. - **Credential handling:** Your Autostore Controller basic credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context. - **Discovery method:** Agents search Jentic by intent such as 'get the contents of a bin' or 'release stock at a transfer port', and Jentic returns the matching operation with its input schema so the agent calls the right endpoint without browsing the reference docs. ## Related APIs - **Shopify** — Alternative e commerce API - **Stripe** — Alternative e commerce API ## FAQ ### What authentication does the Autostore Controller use? The Autostore Controller uses HTTP Basic authentication with username and password. Through Jentic, these credentials are stored encrypted in your Jentic One instance and injected at execution time, so raw secrets never enter the agent context. ### Can I delivers a list of bins with their content information which contains the reques with the Autostore Controller? Yes. Use the GET `/AutoStore/PZN/List/{pzn}` endpoint. The API returns structured JSON responses that agents can parse and act on directly. ### What are the rate limits for the Autostore Controller? Rate limits are not specified in the OpenAPI spec. Check the vendor documentation for current limits. Through Jentic, rate limiting is handled automatically with retry logic built into the execution layer. ### How do I delivers a list of bins with their content information which contains the reques through Jentic? Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'delivers a list of bins with their content information which contains the reques'. Jentic returns the matching Autostore Controller operation with its input schema. Load the schema and execute the call - credentials are injected automatically. ### How many endpoints does the Autostore Controller have? The Autostore Controller exposes 10 endpoints covering autostore, autostore operations. ### Can I limit what my agent is allowed to do with the Autostore Controller API? Yes. Because you run Jentic One yourself, your own rules decide which Autostore Controller operations and credentials the agent may use. Since the bin id sits in the URL path at GET `/Autostore/BinContent/{bin_id}`, you can pin the agent to reading one bin's contents and nothing more, and you choose which operations it can call at all. Write actions such as POST `/AutoStore/ReleaseAtTransferPort` or PUT `/AutoStore/SetCompressMode/{mode}` stay off limits unless you explicitly add them.