Alexfv1603 API-PRODUCTS
Community OpenAPI document · agent-readyE CommerceStorefrontbearer12 EndpointsREST
Know of an official OpenAPI document? Contribute it →
For Agents
Programmatically registro de categoria por sucursal de la empresa, modificacion de categoria por sucursal de la empresa. Covers 12 operations with bearer authentication.
Use for: I need to registro de categoria por sucursal de la empresa, I want to modificacion de categoria por sucursal de la empresa, Search for eliminacion de categoria por sucursal de la empresa, Find all listar categorias por sucursal de la empresa
Not supported: Does not handle payments, communications, or crm - use for e-commerce only.
Gestion de Productos, categorias y marcas. The API exposes 12 endpoints secured with bearer authentication.
Install Jentic One Beta
Connect the API-PRODUCTS to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the API-PRODUCTS, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.alexfv1603%2Fswaggerhub-alexfv1603" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fswaggerhub.alexfv1603%2Fswaggerhub-alexfv1603" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with API-PRODUCTS API.
Registro de categoria por sucursal de la empresa
Modificacion de categoria por sucursal de la empresa
Eliminacion de categoria por sucursal de la empresa
Listar categorias por sucursal de la empresa
Monitor API-PRODUCTS operational status and events
Use Cases
Patterns agents use API-PRODUCTS API for, with concrete tasks.
★ E-Commerce Operations
Use the API-PRODUCTS to perform e commerce operations programmatically. The API provides 12 endpoints covering core functionality including registro de categoria por sucursal de la empresa, modificacion de categoria por sucursal de la empresa, eliminacion de categoria por sucursal de la empresa.
Call POST /categorias to registro de categoria por sucursal de la empresa
Automated Categorias Management
Automate categorias operations by combining multiple API-PRODUCTS endpoints. Agents can modificacion de categoria por sucursal de la empresa and then eliminacion de categoria por sucursal de la empresa in a single workflow.
Call PUT /categorias to modificacion de categoria por sucursal de la empresa, then verify the result
AI Agent Integration via Jentic
AI agents discover and call API-PRODUCTS 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.
Search Jentic for 'registro de categoria por sucursal de la empresa', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
12 endpoints — gestion de productos, categorias y marcas.
METHOD
PATH
DESCRIPTION
POST
/categorias
Registro de categoria por sucursal de la empresa
PUT
/categorias
Modificacion de categoria por sucursal de la empresa
DELETE
/categorias/{id-categoria}
Eliminacion de categoria por sucursal de la empresa
GET
/categorias/{id-sucursal}
Listar categorias por sucursal de la empresa
POST
/marcas
Registro de marcas por empresa
PUT
/marcas
Modificacion de macra de la empresa
DELETE
/marcas/{id-marca}
Eliminacion de marca por empresa
GET
/marcas/{id-empresa}
Listar marcas por empresa
POST
/categorias
Registro de categoria por sucursal de la empresa
PUT
/categorias
Modificacion de categoria por sucursal de la empresa
DELETE
/categorias/{id-categoria}
Eliminacion de categoria por sucursal de la empresa
GET
/categorias/{id-sucursal}
Listar categorias por sucursal de la empresa
POST
/marcas
Registro de marcas por empresa
PUT
/marcas
Modificacion de macra de la empresa
DELETE
/marcas/{id-marca}
Eliminacion de marca por empresa
GET
/marcas/{id-empresa}
Listar marcas por empresa
Why Jentic?
What agents get from Jentic-routed access to this vendor.
Setup
Wiring API-PRODUCTS by hand means setting up its bearer JWT auth and calling category and brand operations yourself against the hosted host, including the create, update, and delete calls. Through Jentic you install once, import API-PRODUCTS from the API Directory, store the bearer token once, and your agent calls it.
Permission scoping
API-PRODUCTS puts the category id and brand id in the URL path (/categorias/{id-categoria}, /marcas/{id-marca}), so a rule can pin your agent to one category or brand: it can read it and nothing else. You choose the operations it may call, so ones that change or remove data like create, update, or delete are not included unless you add them.
Credential isolation
Your API-PRODUCTS 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.
Intent-based discovery
Agents search Jentic by intent such as 'register a category for a branch' or 'list brands for a company', and Jentic returns the matching API-PRODUCTS operation with its input schema so the agent calls the right endpoint without browsing the reference docs.
Related APIs
Alternatives and complements available in the Jentic catalogue.
Alternative
Stripe
Alternative e commerce API
Choose Stripe when you need a different approach to e commerce operations
FAQs
Specific to using API-PRODUCTS API through Jentic.
What authentication does the API-PRODUCTS use?
The API-PRODUCTS 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 registro de categoria por sucursal de la empresa with the API-PRODUCTS?
Yes. Use the POST /categorias endpoint. The API returns structured JSON responses that agents can parse and act on directly.
What are the rate limits for the API-PRODUCTS?
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 registro de categoria por sucursal de la empresa through Jentic?
Install the Jentic SDK with pip install jentic, authenticate through Jentic One, the self-hosted execution layer, then search for 'registro de categoria por sucursal de la empresa'. Jentic returns the matching API-PRODUCTS operation with its input schema. Load the schema and execute the call - credentials are injected automatically.
How many endpoints does the API-PRODUCTS have?
The API-PRODUCTS exposes 12 endpoints covering categorias, marcas, productos operations.
Can I limit what my agent is allowed to do with the API-PRODUCTS?
Yes. Because you run Jentic One yourself, your own rules decide which API-PRODUCTS operations and credentials the agent may use, so you can grant only read calls like GET /categorias/{id-sucursal} or GET /marcas/{id-empresa} and leave out the create, update, and delete operations. Since the category id and brand id sit in the URL path, a rule can pin the agent to a single category or brand and let it read that one and nothing else. The bearer token stays in your instance and is injected only for the operations you have allowed.
GET STARTED