canonical: https://jentic.com/apis/swaggerhub.semantictouch/bentoweb-api

# Semantictouch Bentoweb API

This is an example of using product API. The API exposes 89 endpoints secured with oauth2 authentication.

## For AI agents

Programmatically create new templates, get templates. Covers 89 operations with oauth2 authentication.

## Scope

Does not handle payments, communications, or crm - use for e-commerce only.

## Capabilities

- Create new templates
- Get templates
- Update template
- Delete template
- Monitor Bentoweb API operational status and events

## Use cases

### E-Commerce Operations

Use the Bentoweb API to perform e commerce operations programmatically. The API provides 89 endpoints covering core functionality including create new templates, get templates, get template.

Example prompt: Call POST /category-attribute-template to create new templates

### Automated Products Management

Automate products operations by combining multiple Bentoweb API endpoints. Agents can get templates and then get template in a single workflow.

Example prompt: Call GET /category-attribute-template to get templates, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'create new templates', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/category-attribute-template` | Create new templates |
| GET | `/category-attribute-template` | Get templates |
| GET | `/category-attribute-template/{template_id}` | Get template |
| PUT | `/category-attribute-template/{template_id}` | Update template |
| DELETE | `/category-attribute-template/{template_id}` | Delete template |
| POST | `/category-attribute-topic` | Create new topic |
| GET | `/category-attribute-topic` | Get topics |
| GET | `/category-attribute-topic/{topic_id}` | Get topic |

## Key resources

- **Products** — Operations related to Products
- **Category Attributes** — Operations related to Category Attributes
- **Brand** — Operations related to Brand
- **Content Block** — Operations related to Content Block
- **Stores** — Operations related to Stores

## Why Jentic

- **Setup:** Wiring Bentoweb API by hand means implementing its OAuth2 password flow against login.bentoweb.com, refreshing tokens for the queue.bentoweb.com host, and handling requests and retries yourself. Through Jentic you install once, import Bentoweb API from the API Directory, store the client credentials once, and your agent calls it.
- **Permission scoping:** Bentoweb API puts the template id in the URL path (`/category-attribute-template/{template_id}`), so a rule can pin your agent to one template: it can read that template and nothing else. You choose the operations it may call, so writes like updating or deleting a template are not included unless you add them.
- **Credential handling:** Your Bentoweb API credentials are stored once, encrypted, by your own Jentic One instance and injected at execution time. They never enter the agent's prompt, logs, or context.
- **Discovery method:** Agents search Jentic by intent such as 'list category attribute templates' or 'create a new template', and Jentic returns the matching Bentoweb API operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Shopify** — Alternative e commerce API
- **Stripe** — Alternative e commerce API

## FAQ

### What authentication does the Bentoweb API use?

The Bentoweb API uses OAuth 2.0 for authorization. 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 create new templates with the Bentoweb API?

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

### What are the rate limits for the Bentoweb 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 create new templates through Jentic?

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

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

The Bentoweb API exposes 89 endpoints covering products, category attributes, brand operations.

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

Yes. Because Jentic One is self-hosted, you write the rules that decide which Bentoweb API operations and credentials your agent may use. Since the template id lives in the URL path (`/category-attribute-template/{template_id}`), a rule can pin the agent to a single template so it reads that template and nothing else. You also choose which operations it may call, so writes such as updating or deleting a template stay out of reach unless you explicitly add them.