canonical: https://jentic.com/apis/swaggerhub.plattform-i40/dotaas-part-2-httprest-aasx-file-server-api

# Plattform I40 DotAAS Part 2 | HTTP/REST | AASX File Server API

The AASX file server API as part of Details of the Asset Administration Shell Part 2. The API exposes 5 endpoints.

## For AI agents

Programmatically stores the aasx package at the server, returns a list of available aasx packages at the server. Covers 5 operations.

## Scope

Does not handle payments, communications, or crm - use for cloud infrastructure only.

## Capabilities

- Stores the AASX package at the server
- Returns a list of available AASX packages at the server
- Updates the AASX package at the server
- Deletes a specific AASX package from the server
- Monitor DotAAS Part 2 | HTTP/REST | AASX File Server API operational status and events

## Use cases

### Cloud Infrastructure Operations

Use the DotAAS Part 2 | HTTP/REST | AASX File Server API to perform cloud infrastructure operations programmatically. The API provides 5 endpoints covering core functionality including stores the aasx package at the server, returns a list of available aasx packages at the server, returns a specific aasx package from the server.

Example prompt: Call POST /packages to stores the aasx package at the server

### Automated AASX File Server API Management

Automate aasx file server API operations by combining multiple DotAAS Part 2 | HTTP/REST | AASX File Server API endpoints. Agents can returns a list of available aasx packages at the server and then returns a specific aasx package from the server in a single workflow.

Example prompt: Call GET /packages to returns a list of available aasx packages at the server, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call DotAAS Part 2 | HTTP/REST | AASX File Server 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 'stores the aasx package at the server', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/packages` | Stores the AASX package at the server |
| GET | `/packages` | Returns a list of available AASX packages at the server |
| GET | `/packages/{packageId}` | Returns a specific AASX package from the server |
| PUT | `/packages/{packageId}` | Updates the AASX package at the server |
| DELETE | `/packages/{packageId}` | Deletes a specific AASX package from the server |

## Key resources

- **AASX File Server API** — Operations related to AASX File Server API

## Why Jentic

- **Setup:** Wiring the AASX File Server API by hand means resolving its templated protocol, host, port, and version prefix into a base URL, matching each package path yourself, and parsing the upload and retrieval responses. Through Jentic you install once, import the AASX File Server API from the API Directory, and since it takes no credential your agent calls it straight away.
- **Permission scoping:** The AASX File Server API puts the package id in the URL path (`/packages/{packageId}`), so a rule can pin your agent to one package and nothing else. You choose the operations it may call, so a destructive one like deleting a package is not included unless you add it.
- **Credential handling:** The AASX File Server API needs no credential to call, so there is nothing to store. If you add related services later, any credential is stored once, encrypted, by your own Jentic One instance and injected at execution time, never entering the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'upload an AASX package' or 'fetch a stored package', and Jentic returns the matching AASX File Server API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Amazonaws** — Alternative cloud infrastructure API
- **Azure** — Alternative cloud infrastructure API
- **Googleapis** — Complementary cloud infrastructure API
- **Digitalocean** — Complementary cloud infrastructure API

## FAQ

### What authentication does the DotAAS Part 2 | HTTP/REST | AASX File Server API use?

The DotAAS Part 2 | HTTP/REST | AASX File Server 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 stores the aasx package at the server with the DotAAS Part 2 | HTTP/REST | AASX File Server API?

Yes. Use the POST /packages endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the DotAAS Part 2 | HTTP/REST | AASX File Server 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 stores the aasx package at the server through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'stores the aasx package at the server'. Jentic returns the matching DotAAS Part 2 | HTTP/REST | AASX File Server API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the DotAAS Part 2 | HTTP/REST | AASX File Server API have?

The DotAAS Part 2 | HTTP/REST | AASX File Server API exposes 5 endpoints covering aasx file server API operations.

### Can I limit what my agent is allowed to do with the AASX File Server API?

Yes. Because you run Jentic One yourself, your own rules decide which of the five AASX File Server operations the agent may call, so you can grant read access through GET /packages and GET `/packages/{packageId}` while withholding a destructive one like DELETE `/packages/{packageId}` unless you choose to add it. Since the package id sits in the URL path, a rule can pin the agent to a single package and nothing else. You keep full control over which operations run and on which package.