canonical: https://jentic.com/apis/swaggerhub.datasys/balkoboxy---parcel-api

# Datasys BalíkoBOXy - Parcel API

API systému BalíkoBOXy Slovenské pošty pro předávání informací o zásilkách Changelog: - v1.0.1 (20.9.2022): Doplněny URL pro testovací prostředí Datasys a produkční prostředí Slovenské pošty - v1.0.2 (19.10.2022): Opraven příklad pro POST `/tenant/{tenantId}/parcel.` The API exposes 2 endpoints.

## For AI agents

Programmatically vytvoří nebo aktualizuje informace o zásilkách, vytvoří nebo aktualizuje informace o zásilce. Covers 2 operations.

## Scope

Does not handle payments, communications, or crm - use for developer tools only.

## Capabilities

- Vytvoří nebo aktualizuje informace o zásilkách
- Manage developer tools data programmatically
- Integrate BalíkoBOXy - Parcel API into automated workflows
- Query and filter BalíkoBOXy - Parcel API records by parameters
- Monitor BalíkoBOXy - Parcel API operational status and events

## Use cases

### Developer Tools Operations

Use the BalíkoBOXy - Parcel API to perform developer tools operations programmatically. The API provides 2 endpoints covering core functionality including vytvoří nebo aktualizuje informace o zásilkách, vytvoří nebo aktualizuje informace o zásilce.

Example prompt: Call POST `/tenant/{tenantId}/parcel` to vytvoří nebo aktualizuje informace o zásilkách

### Data Retrieval and Monitoring

Query BalíkoBOXy - Parcel API resources on a schedule to track changes, generate alerts, or feed downstream dashboards. Agents poll relevant endpoints, compare against previous state, and trigger actions when thresholds are crossed.

Example prompt: Poll the primary BalíkoBOXy - Parcel API endpoint, compare response to last known state, and alert if changed

### AI Agent Integration via Jentic

AI agents discover and call BalíkoBOXy - Parcel 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.

Example prompt: Search Jentic for 'vytvoří nebo aktualizuje informace o zásilkách', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/tenant/{tenantId}/parcel` | Vytvoří nebo aktualizuje informace o zásilkách |
| PUT | `/tenant/{tenantId}/parcel/{barcode}` | Vytvoří nebo aktualizuje informace o zásilce |

## Key resources

- **parcel** — Správa zásilek

## Why Jentic

- **Setup:** Wiring the BalikoBOXy Parcel API by hand means choosing among its SwaggerHub and slposta.sk hosts, shaping the parcel create and update calls, and handling retries yourself, even though it takes no auth. Through Jentic you install once, import the BalikoBOXy Parcel API from the API Directory, and your agent calls it with no credential to store.
- **Permission scoping:** This API puts the tenant and barcode in the URL path (`/tenant/{tenantId}/parcel/{barcode}`), so a rule can pin your agent to one tenant's parcels. You choose the operations it may call, so parcel updates are not included unless you add them, leaving creation only.
- **Credential handling:** This API needs no credentials, so there is nothing for the agent to hold. If a call ever required a secret, your own Jentic One instance would store it once, encrypted, and inject it at execution time so it never enters the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'create a parcel record' or 'update a parcel by barcode', and Jentic returns the matching BalikoBOXy Parcel API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Github** — Alternative developer tools API
- **Gitlab** — Alternative developer tools API

## FAQ

### What authentication does the BalíkoBOXy - Parcel API use?

The BalíkoBOXy - Parcel 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 vytvoří nebo aktualizuje informace o zásilkách with the BalíkoBOXy - Parcel API?

Yes. Use the POST `/tenant/{tenantId}/parcel` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the BalíkoBOXy - Parcel 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 vytvoří nebo aktualizuje informace o zásilkách through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'vytvoří nebo aktualizuje informace o zásilkách'. Jentic returns the matching BalíkoBOXy - Parcel API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the BalíkoBOXy - Parcel API have?

The BalíkoBOXy - Parcel API exposes 2 endpoints covering parcel operations.

### Can I limit what my agent is allowed to do with the BalikoBOXy Parcel API?

Yes. Jentic One is self-hosted, so you write the rules that decide which of this API's operations your agent may call. Because the tenant and barcode sit in the URL path, such as POST `/tenant/{tenantId}/parcel` and PUT `/tenant/{tenantId}/parcel/{barcode}`, you can pin the agent to a single tenant's parcels and grant only the operations you intend. If you allow parcel creation but withhold the update endpoint, the agent can create records without editing existing ones by barcode.