canonical: https://jentic.com/apis/swaggerhub.insolutionsdev2/acres-api-documentation

# Insolutionsdev2 Acres API Documentation

REST API para la aplicación de Acres. The API exposes 9 endpoints.

## For AI agents

Programmatically mejores huellas, validación biométrica. Covers 9 operations.

## Scope

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

## Capabilities

- Mejores huellas
- Validación biométrica
- Obtener documentos firmados
- Generacion de documento
- Creación de usuario
- Cambiar contraseña

## Use cases

### Developer Tools Operations

Use the Acres API Documentation to perform developer tools operations programmatically. The API provides 9 endpoints covering core functionality including mejores huellas, validación biométrica, obtener documentos firmados.

Example prompt: Call POST /api/v1/biometrics/best to mejores huellas

### Automated Biometrics Management

Automate biometrics operations by combining multiple Acres API Documentation endpoints. Agents can validación biométrica and then obtener documentos firmados in a single workflow.

Example prompt: Call POST /api/v1/biometrics/validation to validación biométrica, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Acres API Documentation 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 'mejores huellas', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | /api/v1/biometrics/best | Mejores huellas |
| POST | /api/v1/biometrics/validation | Validación biométrica |
| GET | /api/v1/documents/signed | Obtener documentos firmados |
| GET | /api/v1/documents/pending/{documentId} | Obtener documentos pendientes de firma por su id |
| POST | /api/v1/documents/generation | Generacion de documento |
| POST | /api/v1/users | Creación de usuario |
| PATCH | /api/v1/users | Cambiar contraseña |
| GET | /api/v1/users/{dni} | Comprobación de DNI |

## Key resources

- **Biometrics** — Operations for biometrics
- **Documents** — Operations for documents
- **Users** — Operations for users

## Why Jentic

- **Setup:** Wiring the Acres API by hand means reading its spec, building calls across its biometrics, documents, and users endpoints, and handling request formatting and retries yourself. Through Jentic you install once, import Acres from the API Directory, store any required connection detail once, and your agent calls it.
- **Permission scoping:** Acres puts the document id and user dni in the URL path (/api/v1/documents/pending/{documentId}, /api/v1/users/{dni}), so a rule can pin your agent to reading one document or one user. You choose the operations it may call, so write operations like user creation or the PATCH update are not included unless you add them.
- **Credential handling:** Any connection detail the Acres API needs 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 best biometric fingerprints' or 'check a pending document', and Jentic returns the matching Acres 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 Acres API Documentation use?

The Acres API Documentation 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 mejores huellas with the Acres API Documentation?

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

### What are the rate limits for the Acres API Documentation?

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 mejores huellas through Jentic?

Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'mejores huellas'. Jentic returns the matching Acres API Documentation operation with its input schema. Load the schema and execute the call - credentials are injected automatically.

### How many endpoints does the Acres API Documentation have?

The Acres API Documentation exposes 9 endpoints covering biometrics, documents, users operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which Acres operations and credentials the agent may use. The Acres API puts the document id and user DNI in the URL path (/api/v1/documents/pending/{documentId} and /api/v1/users/{dni}), so a rule can pin the agent to reading a single document or a single user. You choose which operations are exposed, so write calls such as user creation (POST /api/v1/users) or the PATCH password change stay out of reach unless you add them.