canonical: https://jentic.com/apis/swaggerhub.evana-ag/evana360-api

# Evana Ag Evana360 API

API to consume Evana360's logic. The API exposes 51 endpoints secured with bearer authentication.

## For AI agents

Programmatically validate user's username and password, gets a user access token.. Covers 51 operations with bearer authentication.

## Scope

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

## Capabilities

- Validate user's username and password
- Gets a user access token.
- Upload a binary file
- Download the specified binary file
- Delete the specified binary file
- Get the data model content (all keys) of the document

## Use cases

### Developer Tools Operations

Use the Evana360 API to perform developer tools operations programmatically. The API provides 51 endpoints covering core functionality including validate user's username and password, gets a user access token., upload a binary file.

Example prompt: Call POST `/v1.0.0/authenticate` to validate user's username and password

### Automated authentication Management

Automate authentication operations by combining multiple Evana360 API endpoints. Agents can gets a user access token. and then upload a binary file in a single workflow.

Example prompt: Call POST `/v1.0.0/login` to gets a user access token., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Evana360 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 bearer tokens manually.

Example prompt: Search Jentic for 'validate user's username and password', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v1.0.0/authenticate` | Validate user's username and password |
| POST | `/v1.0.0/login` | Gets a user access token. |
| POST | `/v1.0.0/files` | Upload a binary file |
| GET | `/v1.0.0/files/{id}` | Download the specified binary file |
| PUT | `/v1.0.0/files/{id}` | Upload a new version of the specified binary file |
| DELETE | `/v1.0.0/files/{id}` | Delete the specified binary file |
| GET | `/v1.0.0/files/{id}/analysis` | Get the data model content (all keys) of the document |
| GET | `/v1.0.0/files/{id}/masterData` | Get the elements assigned to the document |

## Key resources

- **authentication** — Validation of user objects to obtain an access token
- **binary files** — Manage binary files within Evana360
- **documents** — Manage documents. Documents are directly related to binary files
- **structures** — Manage structures
- **keys** — Manage keys (key-value pairs of data models) of files and elements

## Why Jentic

- **Setup:** Wiring the Evana360 API by hand means obtaining its bearer token through the authenticate flow, choosing between the sandbox and production Evana hosts, and handling responses yourself. Through Jentic you install once, import the Evana360 API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The Evana360 API puts the file id in the URL path (`/v1.0.0/files/{id}/...`), so a rule can pin your agent to one file: it can read that file and its analysis and master data and nothing else. You choose the operations it may call, so file deletion is not included unless you add it.
- **Credential handling:** Your Evana360 API bearer token 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.
- **Discovery method:** Agents search Jentic by intent such as 'get the analysis for a file' or 'upload a file', and Jentic returns the matching Evana360 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 Evana360 API use?

The Evana360 API uses a Bearer token in the Authorization header. 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 validate user's username and password with the Evana360 API?

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

### What are the rate limits for the Evana360 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 validate user's username and password through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'validate user's username and password'. Jentic returns the matching Evana360 API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Evana360 API have?

The Evana360 API exposes 51 endpoints covering authentication, binary files, documents operations.

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

Yes. Because you self-host Jentic One, your own rules decide which Evana360 API operations and credentials the agent may use. Since the API puts the file id in the URL path (`/v1.0.0/files/{id}/...`), you can pin the agent to a single file so it only reads that file, its analysis, and its master data. You choose the operations it may call, so destructive actions like deleting a binary file are excluded unless you explicitly allow them.