canonical: https://jentic.com/apis/swaggerhub.coria9404-1/api-de-gestin-de-categoras

# Coria9404 1 Category Management API

An API to retrieve, add, edit, and delete categories. The API exposes 4 endpoints.

## For AI agents

Programmatically access Category Management API resources. Covers 4 operations.

## Scope

Does not handle payments, communications, or crm - use for category management only.

## Capabilities

- Access Category Management API resources via REST API
- Manage category data programmatically
- Integrate Category Management API into automated workflows
- Query and filter Category Management API records by parameters
- Monitor Category Management API operational status and events

## Use cases

### Category Management Operations

Use the Category Management API to perform category management operations programmatically. The API provides 4 endpoints covering core functionality including retrieving all categories, adding a new category, editing a category by ID.

Example prompt: Execute a primary operation against the Category Management API

### Automated Category Workflows

Automate category operations by combining multiple Category Management API endpoints. Agents can add a new category and then edit a category by ID in a single workflow.

Example prompt: Add a new category and then update it via the Category Management API

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'category management API', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | `/categoria` | Get all categories |
| POST | `/categoriaAgregar` | Add a new category |
| PUT | `/categoriaEditar{categoriaId}` | Edit a category by ID |
| DELETE | `/categoriaEliminar{categoriaId}` | Delete a category by ID |

## Key resources

- **Categories** — Operations related to categories
- **Add Category** — Operations related to adding categories
- **Edit Category** — Operations related to editing categories
- **Delete Category** — Operations related to deleting categories

## Why Jentic

- **Setup:** Wiring the Category Management API by hand means pointing at its SwaggerHub mock host, matching the add, edit, and delete request formats, and handling responses yourself even though it takes no auth. Through Jentic you install once, import the Category Management API from the API Directory, store any connection detail once, and your agent calls it.
- **Permission scoping:** This API carries the category id in the URL path for edit and delete, so a rule can pin your agent to reading categories: you choose the operations it may call, so write operations like adding, editing, or deleting a category are not included unless you add them.
- **Credential handling:** Any Category Management API connection detail 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 'list categories' or 'add a category', and Jentic returns the matching Category Management 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 Category Management API use?

The Category Management API uses none 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.

### What are the rate limits for the Category Management 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 use category management API through Jentic?

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

### How many endpoints does the Category Management API have?

The Category Management API exposes 4 endpoints covering categories operations.

### Does the Category Management API support pagination?

Pagination support depends on the specific endpoint. Check the endpoint parameters for page, limit, or offset fields. Through Jentic, the operation schema exposes all available parameters so agents can paginate automatically.

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

Yes. Because you self-host Jentic One, your own rules decide which Category Management API operations and credentials the agent may use. You can pin the agent to reading categories with the GET categories operation and leave out the write operations, so adding, editing, or deleting a category is off limits unless you explicitly grant it. Since the category id travels in the URL path on the edit and delete calls, you keep full control over whether those destructive operations are ever exposed to the agent.