canonical: https://jentic.com/apis/owllee.io/owllee

# Owllee API

OWLLEE is virtual assistant software, a smart bridge between businesses and customers. This API provides endpoints for managing chatbots, conversations, and chat messages. The API exposes 9 endpoints secured with bearer authentication.

## For AI agents

Programmatically create a chatbot, get list of chatbots. Covers 9 operations with bearer authentication.

## Scope

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

## Capabilities

- Create a chatbot
- Get list of chatbots
- List conversations for a chatbot
- Update a conversation
- Delete a conversation

## Use cases

### Communications Operations

Use the Owllee API to perform communications operations programmatically. The API provides 9 endpoints covering core functionality including create a chatbot, get list of chatbots, get a chatbot.

Example prompt: Call POST `/api/chatbot` to create a chatbot

### Automated Chatbot Management

Automate chatbot operations by combining multiple Owllee API endpoints. Agents can get list of chatbots and then get a chatbot in a single workflow.

Example prompt: Call GET `/api/chatbot` to get list of chatbots, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Owllee 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 'create a chatbot', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/api/chatbot` | Create a chatbot |
| GET | `/api/chatbot` | Get list of chatbots |
| GET | `/api/chatbot/{id}` | Get a chatbot |
| GET | `/api/{chatbot_id}/chatbot/conversations` | List conversations for a chatbot |
| GET | `/api/conversations/{idx}` | Get a conversation |
| PUT | `/api/conversations/{idx}` | Update a conversation |
| DELETE | `/api/conversations/{idx}` | Delete a conversation |
| GET | `/api/conversations/{conversation_id}/chat-messages` | Get chat messages for a conversation |

## Key resources

- **Chatbot** — Chatbot management operations
- **Conversations** — Conversation management operations
- **Chat** — Chat messaging operations

## Why Jentic

- **Setup:** Wiring Owllee by hand means carrying its JWT bearer token on every chatbot and conversation call and paging chat messages yourself. Through Jentic you install once, import the Owllee API from the API Directory, store the token once, and your agent calls it.
- **Permission scoping:** Owllee puts the chatbot and conversation ids in the URL path (`/api/chatbot/{id}`, `/api/conversations/{idx}`), so a rule can pin your agent to one chatbot or conversation for reads like listing conversations and messages. You choose the operations it may call, so updating or deleting a conversation is not included unless you add it.
- **Credential handling:** Your Owllee 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 chatbot' or 'read a conversation's messages', and Jentic returns the matching Owllee operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Twilio** — Alternative communications API
- **Sendgrid** — Alternative communications API
- **Pusher** — Complementary communications API

## FAQ

### What authentication does the Owllee API use?

The Owllee 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 create a chatbot with the Owllee API?

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

### What are the rate limits for the Owllee 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 a chatbot through Jentic?

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

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

The Owllee API exposes 9 endpoints covering chatbot, conversations, chat operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Owllee operations and credentials your agent may use. Owllee puts the chatbot and conversation ids in the URL path (`/api/chatbot/{id}`, `/api/conversations/{idx}`), so you can pin the agent to a single chatbot or conversation and restrict it to reads like listing conversations and fetching chat messages. Only the operations you approve are callable, so updating or deleting a conversation stays off limits unless you explicitly allow it.