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

# Evana Ag Evana360 API v2

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

## For AI agents

Programmatically delivers the user regarding the requested id., partially updates the user regarding the requested id.. Covers 36 operations with bearer authentication.

## Scope

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

## Capabilities

- Delivers the user regarding the requested id.
- Partially updates the user regarding the requested id.
- A element will be created at a specified structure
- Updating a elements values partially
- Based on the access rights of the user, an attempt is made to delete an element

## Use cases

### Developer Tools Operations

Use the Evana360 API v2 to perform developer tools operations programmatically. The API provides 36 endpoints covering core functionality including delivers the user regarding the requested id., partially updates the user regarding the requested id., a element will be created at a specified structure.

Example prompt: Call GET `/users/{id}` to delivers the user regarding the requested id.

### Automated Element Management Management

Automate element management operations by combining multiple Evana360 API v2 endpoints. Agents can partially updates the user regarding the requested id. and then a element will be created at a specified structure in a single workflow.

Example prompt: Call PATCH `/users/{id}` to partially updates the user regarding the requested id., then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Evana360 API v2 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 'delivers the user regarding the requested id.', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/users/{id}` | Delivers the user regarding the requested id. |
| PATCH | `/users/{id}` | Partially updates the user regarding the requested id. |
| POST | `/elements` | A element will be created at a specified structure |
| GET | `/elements` | Delivers all available elements which are available for the current user. to nar |
| GET | `/elements/{id}` | Delivers the element which are available for the current user regarding the requ |
| PATCH | `/elements/{id}` | Updating a elements values partially |
| DELETE | `/elements/{id}` | Based on the access rights of the user, an attempt is made to delete an element |
| GET | `/documents` | Delivers all available documents which are available for the current user. to na |

## Key resources

- **Element Management** — Manage elements (former master data)
- **Document Management** — Manage documents within Evana360
- **User Management** — Manage users within Evana360
- **Structure Management** — Manage structures within Evana360
- **Index Management** — Manage indices within Evana360

## Why Jentic

- **Setup:** Wiring the Evana360 API v2 by hand means passing its bearer token, choosing between the sandbox and production Evana gateway hosts, and handling responses yourself. Through Jentic you install once, import the Evana360 API v2 from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The Evana360 API v2 puts the resource id in the URL path (`/elements/{id}`, `/documents/{id}`), so a rule can pin your agent to one element or document: it can read and patch that resource and nothing else. You choose the operations it may call, so element deletion is not included unless you add it.
- **Credential handling:** Your Evana360 API v2 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 a user by id' or 'create an element', and Jentic returns the matching Evana360 API v2 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 v2 use?

The Evana360 API v2 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 delivers the user regarding the requested id. with the Evana360 API v2?

Yes. Use the GET `/users/{id}` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Evana360 API v2?

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 the user regarding the requested id. through Jentic?

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

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

The Evana360 API v2 exposes 36 endpoints covering element management, document management, user management operations.

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

Yes. Because Jentic One is self-hosted and you set its rules, you choose exactly which Evana360 API v2 operations your agent may call and which bearer credentials it may use. Since the API puts the resource id in the URL path, such as `/elements/{id}` and `/documents/{id}`, you can pin the agent to a single element or document and allow only reads and partial updates on it. Destructive operations like DELETE `/elements/{id}` stay out of scope unless you explicitly grant them.