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

# Sendbee AI Number API

AI Number (formerly Sendbee) API for managing teams, contacts, conversations, and messaging via WhatsApp. The API exposes 20 endpoints secured with apiKey authentication.

## For AI agents

Programmatically list teams, list team members. Covers 20 operations with apiKey authentication.

## Scope

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

## Capabilities

- List teams
- Create contact
- Update contact
- Query and filter AI Number API records by parameters
- Monitor AI Number API operational status and events

## Use cases

### Communications Operations

Use the AI Number API to perform communications operations programmatically. The API provides 20 endpoints covering core functionality including list teams, list team members, create contact.

Example prompt: Call GET /teams/teams to list teams

### Automated Contact Fields Management

Automate contact fields operations by combining multiple AI Number API endpoints. Agents can list team members and then create contact in a single workflow.

Example prompt: Call GET /teams/members to list team members, then verify the result

### AI Agent Integration via Jentic

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

Example prompt: Search Jentic for 'list teams', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| GET | /teams/teams | List teams |
| GET | /teams/members | List team members |
| POST | /contacts/subscribe | Create contact |
| GET | /contacts | List contacts |
| PUT | /contacts | Update contact |
| POST | /contacts/tags | Create contact tag |
| GET | /contacts/tags | List contact tags |
| PUT | /contacts/tags | Update contact tag |

## Key resources

- **Contact Fields** — Operations related to Contact Fields
- **Contact Tags** — Operations related to Contact Tags
- **Contacts** — Operations related to Contacts
- **Conversations** — Operations related to Conversations
- **Messages** — Operations related to Messages

## Why Jentic

- **Setup:** Wiring the AI Number API by hand means learning its header key auth, calling api-v2.sendbee.io, and managing contact and tag payloads yourself. Through Jentic you install once, import the AI Number API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The AI Number API carries contact and tag details in the request body, so scoping stays operations-only: limit the agent to the operations it needs, such as subscribing a contact or listing teams. You choose the operations it may call, so tag deletion is not included unless you add it.
- **Credential handling:** Your AI Number API key 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 teams' or 'subscribe a contact', and Jentic returns the matching AI Number API 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 AI Number API use?

The AI Number API uses an API key passed in the `authToken` 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 list teams with the AI Number API?

Yes. Use the GET /teams/teams endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the AI Number 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 list teams through Jentic?

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

### How many endpoints does the AI Number API have?

The AI Number API exposes 20 endpoints covering contact fields, contact tags, contacts operations.

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

Yes. Jentic One runs self-hosted, so your own rules decide which AI Number API operations and credentials the agent may use. Because contact and tag details travel in the request body, scoping is operations-only: you can allow the agent to list teams, list team members, and subscribe or update a contact while withholding higher-risk calls like deleting a contact tag. Only the operations you explicitly grant are callable, and the stored API key is injected at execution time rather than exposed to the agent.