Zeyos Ballsportdirekt KICKZ API
Browse all Swaggerhub Zeyos APIsCommunity OpenAPI document · agent-readyDeveloper ToolsSource Controlnone4 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically get stock, get order status. Covers 4 operations.
Use for: I need to stock, I want to order status, Search for order, Find all cancel order
Not supported: Does not handle payments, communications, or crm - use for developer tools only.
Ballsportdirekt KICKZ API. The API exposes 4 endpoints.
Install Jentic One Beta
Connect the Ballsportdirekt KICKZ API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Ballsportdirekt KICKZ API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.zeyos%2Fballsportdirekt-kickz-api" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.zeyos%2Fballsportdirekt-kickz-api" | sh
jentic register # connects your agent to your Jentic One instanceJentic 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 Ballsportdirekt KICKZ API.
Get Stock
Create Order
Cancel Order
Query and filter Ballsportdirekt KICKZ API records by parameters
Monitor Ballsportdirekt KICKZ API operational status and events
Use Cases
Patterns agents use Ballsportdirekt KICKZ API for, with concrete tasks.
★ Developer Tools Operations
Use the Ballsportdirekt KICKZ API to perform developer tools operations programmatically. The API provides 4 endpoints covering core functionality including get stock, get order status, create order.
Call GET /stock to get stock
Automated order Management
Automate order operations by combining multiple Ballsportdirekt KICKZ API endpoints. Agents can get order status and then create order in a single workflow.
Call GET /order/{REF} to get order status, then verify the result
AI Agent Integration via Jentic
AI agents discover and call Ballsportdirekt KICKZ API 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 none tokens manually.
Search Jentic for 'get stock', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — ballsportdirekt kickz api.
METHOD
PATH
DESCRIPTION
GET
/stock
Get Stock
GET
/order/{REF}
Get Order Status
PUT
/order/{REF}
Create Order
DELETE
/order/{REF}
Cancel Order
GET
/stock
Get Stock
GET
/order/{REF}
Get Order Status
PUT
/order/{REF}
Create Order
DELETE
/order/{REF}
Cancel Order
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring the Ballsportdirekt KICKZ API by hand means coding its stock and order calls against its host and shaping each order payload yourself. Through Jentic you install once, import the Ballsportdirekt KICKZ API from the API Directory, and your agent calls it.
Permission scoping
The KICKZ API puts the order reference in the URL path (/order/{REF}), so a rule can pin your agent to one order: it can read that order and nothing else. You choose the operations it may call, so destructive ones like deleting an order are not included unless you add them.
Credential isolation
Any credential you configure for the Ballsportdirekt KICKZ API 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.
Intent-based discovery
Agents search Jentic by intent such as 'get current stock' or 'update an order', and Jentic returns the matching Ballsportdirekt KICKZ API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Ballsportdirekt KICKZ API through Jentic.
What authentication does the Ballsportdirekt KICKZ API use?
The Ballsportdirekt KICKZ API uses no authentication. 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 get stock with the Ballsportdirekt KICKZ API?
Yes. Use the GET /stock endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the Ballsportdirekt KICKZ API?
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 get stock through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'get stock'. Jentic returns the matching Ballsportdirekt KICKZ API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the Ballsportdirekt KICKZ API have?
The Ballsportdirekt KICKZ API exposes 4 endpoints covering order, stock operations.
Can I limit what my agent is allowed to do with the Ballsportdirekt KICKZ API?
Yes. Because you run Jentic One yourself, your own rules decide which of the Ballsportdirekt KICKZ API operations the agent may call, so you can grant read-only access to GET /stock and GET /order/{REF} while withholding PUT /order/{REF} and DELETE /order/{REF}. Since the order reference sits in the URL path (/order/{REF}), a rule can also pin the agent to a single order so it reads that one and nothing else. Destructive calls like cancelling an order stay out of reach unless you explicitly add them.
GET STARTED