canonical: https://jentic.com/apis/tallbob.com/tallbob

# Tall Bob API

Tall Bob SMS, MMS, and messaging API for sending and managing communications, contacts, campaigns, and webhooks. The API exposes 48 endpoints secured with basic authentication.

## For AI agents

Programmatically send chat sms, create new contact. Covers 48 operations with basic authentication.

## Scope

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

## Capabilities

- Send Chat SMS
- Create New Contact
- View Contact Details
- Delete Contact
- Find Contact By External ID
- List Contacts

## Use cases

### CRM Operations

Use the Tall Bob API to perform crm operations programmatically. The API provides 48 endpoints covering core functionality including send chat sms, create new contact, view contact details.

Example prompt: Call POST `/v2/chat/send/sms` to send chat sms

### Automated Account Management

Automate account operations by combining multiple Tall Bob API endpoints. Agents can create new contact and then view contact details in a single workflow.

Example prompt: Call POST `/v2/contacts` to create new contact, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Tall Bob 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 basic tokens manually.

Example prompt: Search Jentic for 'send chat sms', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/v2/chat/send/sms` | Send Chat SMS |
| POST | `/v2/contacts` | Create New Contact |
| GET | `/v2/contacts/{contact_id}` | View Contact Details |
| DELETE | `/v2/contacts/{contact_id}` | Delete Contact |
| POST | `/v2/contacts/find` | Find Contact By External ID |
| GET | `/v2/contacts/` | List Contacts |
| GET | `/v2/contacts/{contact_id}/campaigns` | List Contact Campaigns |
| PUT | `/v2/contacts/{contact_id}/metadata` | Upsert Contact Metadata |

## Key resources

- **Account** — Operations related to Account
- **Chat** — Operations related to Chat
- **Contact Lists** — Operations related to Contact Lists
- **Contacts** — Operations related to Contacts
- **Longcodes** — Operations related to Longcodes

## AI readiness

This API is usable in Jentic One now. Its AI-readiness score against Jentic's framework shows where it stands today and where improvements would make it even easier for agents to use.

- **Score:** 39 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 48 / 100
  - Developer Experience & Jentic Compatibility: 61 / 100
  - AI-Readiness & Agent Experience: 55 / 100
  - Agent Usability: 94 / 100
  - Security: 10 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/tallbob.com/tallbob/scorecard
- **How the score is calculated:** https://docs.jentic.com/reference/api-readiness-framework/overview/
- **More about the dimensions:** https://docs.jentic.com/reference/api-readiness-framework/specification/#dimensional-model-overview

### Score it yourself

Every API in the directory is allowlisted, so you can re-score it with no key required.

- **Score your own API:** https://jentic.com/scorecard.md
- **Scoring CLI agent skill:** https://github.com/jentic/jentic-api-scorecard/blob/main/skills/jentic-api-scorecard/SKILL.md

```sh
npx @jentic/api-scorecard-cli score <openapi-url>
```

## Why Jentic

- **Setup:** Wiring the Tall Bob API by hand means setting up HTTP basic auth with your API username and key, sending it on every call, and threading contact ids through nested campaign and metadata routes yourself. Through Jentic you install once, import the Tall Bob API from the API Directory, store the basic credential once, and your agent calls it.
- **Permission scoping:** Tall Bob puts the contact id in the URL path (`/v2/contacts/{contact_id}/...`), so a rule can pin your agent to one contact: it can read that contact and its campaigns and nothing else. You choose the operations it may call, so deleting a contact or sending SMS is not included unless you add it.
- **Credential handling:** Your Tall Bob basic credential 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 'send an SMS' or 'find a contact', and Jentic returns the matching Tall Bob operation with its input schema so the agent calls the right endpoint without browsing the reference docs.

## Related APIs

- **Hubspot** — Alternative crm API
- **Salesforce** — Alternative crm API
- **Pipedrive** — Complementary crm API
- **Zoho** — Complementary crm API

## FAQ

### What authentication does the Tall Bob API use?

The Tall Bob API uses HTTP Basic authentication with username and password. 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 send chat sms with the Tall Bob API?

Yes. Use the POST `/v2/chat/send/sms` endpoint. The API returns structured JSON responses that agents can parse and act on directly.

### What are the rate limits for the Tall Bob 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 send chat sms through Jentic?

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

### How many endpoints does the Tall Bob API have?

The Tall Bob API exposes 48 endpoints covering account, chat, contact lists operations.

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

Yes. Because Jentic One is self-hosted by you, your own rules decide which Tall Bob operations and credentials the agent may use. Since the contact id sits in the URL path (`/v2/contacts/{contact_id}/...`), you can pin the agent to a single contact so it only reads that contact and its campaigns and nothing else. Operations like deleting a contact or sending an SMS via POST `/v2/chat/send/sms` are not available to the agent unless you explicitly add them.