canonical: https://jentic.com/apis/swaggerhub.esignabox/swaggerhub-esignabox

# Esignabox Admin API

API de gestión de licencias de eSignaBox. The API exposes 10 endpoints secured with bearer authentication.

## For AI agents

Programmatically crea una nueva organización, buscar organizaciones. Covers 10 operations with bearer authentication.

## Scope

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

## Capabilities

- crea una nueva organización
- buscar organizaciones
- Otiene la información de una organización
- Actualiza los datos de una organización
- Realiza una accion sobre la organización indicada
- añade un usuario a una organización
- Obtiene los usuarios de una organización

## Use cases

### Developer Tools Operations

Use the Admin API to perform developer tools operations programmatically. The API provides 10 endpoints covering core functionality including crea una nueva organización, buscar organizaciones, otiene la información de una organización.

Example prompt: Call POST /organizations to crea una nueva organización

### Automated Organizations Management

Automate organizations operations by combining multiple Admin API endpoints. Agents can buscar organizaciones and then otiene la información de una organización in a single workflow.

Example prompt: Call GET /organizations to buscar organizaciones, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Admin 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 'crea una nueva organización', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/organizations` | crea una nueva organización |
| GET | `/organizations` | buscar organizaciones |
| GET | `/organizations/{orgId}` | Otiene la información de una organización |
| PUT | `/organizations/{orgId}` | Actualiza los datos de una organización |
| POST | `/organizations/{orgId}/action` | Realiza una accion sobre la organización indicada |
| POST | `/organizations/{orgId}/users` | añade un usuario a una organización |
| GET | `/organizations/{orgId}/users` | Obtiene los usuarios de una organización |
| GET | `/users/{userId}` | Otiene la información de un usuario |

## Key resources

- **Organizations** — Operations for organizations
- **Users** — Operations for users

## Why Jentic

- **Setup:** Wiring the Admin API by hand means passing its JWT bearer token, choosing between the integration and production esignabox hosts, and handling responses yourself. Through Jentic you install once, import the Admin API from the API Directory, store the bearer token once, and your agent calls it.
- **Permission scoping:** The Admin API puts the organization id in the URL path (`/organizations/{orgId}/...`), so a rule can pin your agent to one organization: it can read that org and manage its users and nothing else. You choose the operations it may call, so the organization action and update operations are not included unless you add them.
- **Credential handling:** Your Admin 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 'create a new organization' or 'add a user to an organization', and Jentic returns the matching Admin 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 Admin API use?

The Admin 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 crea una nueva organización with the Admin API?

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

### What are the rate limits for the Admin 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 crea una nueva organización through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'crea una nueva organización'. Jentic returns the matching Admin API operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

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

The Admin API exposes 10 endpoints covering organizations, users operations.

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

Yes. Jentic One is self-hosted, so your own rules decide which Admin API operations and credentials the agent may use. Because the organization id sits in the URL path (`/organizations/{orgId}/...`), a rule can pin the agent to a single organization and let it read that org and manage its users while blocking everything else. You choose the operations it may call, so the update-organization and organization-action endpoints stay off unless you explicitly add them.