Autostore Controller

Name: Autostore Controller API
Brand: Autostore Controller
Availability: InStock

★ Only Publicly Available OpenAPI DocumentE CommerceStorefrontbasic10 EndpointsREST

For 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.

Connect the Autostore Controller to your agent

Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Autostore Controller, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.

Install Jentic One Beta (Self-Hosted)

Jentic One Host machine

# On the machine that will host your Jentic One instance:
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh

Agent machine

# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL https://raw.githubusercontent.com/jentic/jentic-one/main/tools/install.sh | sh
jentic register       # connects your agent to your Jentic One instance

Jentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.

Capabilities

What an agent can do with Autostore Controller API.

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

GET STARTED

Start building with Autostore Controller API

Explore with Jentic

View OpenAPI Document

Use Cases

Patterns agents use Autostore Controller API for, with concrete tasks.

★ 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.

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.

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.

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

10 endpoints — autostore api für ein-/auslagerung/kommissionierung.

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

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

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Autostore Controller basic credentials are stored encrypted in the Jentic vault (MAXsystem). Agents receive scoped access tokens — raw secrets never enter the agent context.

Intent-based discovery

Agents search by intent (e.g., 'delivers a list of bins with their content information which contains the reques') and Jentic returns the matching Autostore Controller operation with its input schema, so the agent can call the right endpoint without browsing docs.

Time to first call

Direct Autostore Controller integration: 1-3 days for auth handling, response parsing, and error cases. Through Jentic: under 1 hour — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Shopify

Alternative e commerce API

Choose Shopify when you need a different approach to e commerce operations

Alternative

Stripe

Alternative e commerce API

Choose Stripe when you need a different approach to e commerce operations

FAQs

Specific to using Autostore Controller API through Jentic.

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 the MAXsystem vault 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 at https://app.jentic.com/sign-up, 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.