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

# SendMsg API

SendMsg is an SMS messaging platform. The API provides access to SMS sending, delivery tracking, contacts, and messaging campaigns. The API exposes 13 endpoints secured with apiKey authentication.

## For AI agents

Programmatically send message, list messages. Covers 13 operations with apiKey authentication.

## Scope

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

## Capabilities

- Send Message
- List Messages
- Get Message
- Create Contact
- Monitor SendMsg API operational status and events

## Use cases

### CRM Operations

Use the SendMsg API to perform crm operations programmatically. The API provides 13 endpoints covering core functionality including send message, list messages, get message.

Example prompt: Call POST /messages to send message

### Automated Messages Management

Automate messages operations by combining multiple SendMsg API endpoints. Agents can list messages and then get message in a single workflow.

Example prompt: Call GET /messages to list messages, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call SendMsg 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 'send message', load the operation schema, and execute with Jentic-managed credentials

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/messages` | Send Message |
| GET | `/messages` | List Messages |
| GET | `/messages/{message_id}` | Get Message |
| POST | `/messages/bulk` | Send Bulk Messages |
| POST | `/contacts` | Create Contact |
| GET | `/contacts` | List Contacts |
| GET | `/contacts/{contact_id}` | Get Contact |
| PUT | `/contacts/{contact_id}` | Update Contact |

## Key resources

- **Messages** — SMS message operations
- **Contacts** — Contact management
- **Campaigns** — SMS campaign management
- **Account** — Account operations

## 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:** 65 / 100
- **Maturity:** AI-Aware
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 57 / 100
  - AI-Readiness & Agent Experience: 48 / 100
  - Agent Usability: 94 / 100
  - Security: 50 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/sendmsg.com/sendmsg/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 SendMsg API by hand means setting up its X-API-Key header auth against api.sendmsg.com/v4 and handling status codes yourself. Through Jentic you install once, import the SendMsg API from the API Directory, store the key once, and your agent calls it.
- **Permission scoping:** The SendMsg API puts the message and contact ids in the URL path (`/messages/{message_id}` and `/contacts/{contact_id}`), so a rule can pin your agent to one contact or message. You choose the operations it may call, so ones that change state like updating a contact are not included unless you add them.
- **Credential handling:** Your SendMsg 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 'send a message to a contact', and Jentic returns the matching SendMsg 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 SendMsg API use?

The SendMsg API uses an API key passed in the `X-API-Key` 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 send message with the SendMsg API?

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

### What are the rate limits for the SendMsg 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 message through Jentic?

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

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

The SendMsg API exposes 13 endpoints covering messages, contacts, campaigns operations.

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

Yes. Because you run Jentic One yourself, your own rules decide which SendMsg operations and credentials the agent may use. Since the API puts message and contact ids in the URL path, such as `/messages/{message_id}` and `/contacts/{contact_id}`, you can pin the agent to a single contact or message. You also pick the operations it can call, so state-changing ones like updating a contact stay out of reach unless you grant them.