canonical: https://jentic.com/apis/smsapi.telintel.net/smsapi-telintel

# Smsapi Telintel Telintel SMS Gateway HTTP API

This service is intended for live traffic, it is scoped for notification systems. It works synchronously (the answer of each message will contain the termination answer, and the message ID), but it may receive several requests simultaneously. Telintel LTD provides an HTTP API to send and receive SMS. It requires an application capable of reading JSON objects, GET/POST request, Authentication crede. The API exposes 4 endpoints.

## For AI agents

Programmatically sendsinglesms_messagedelivery, sendmasssms_notificationservice. Covers 4 operations.

## Scope

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

## Capabilities

- SendSingleSms_messageDelivery
- SendMassSms_notificationService
- DeliveryReceipt_confirmDeliveryReceipt
- ReceiveMessage_callbackResponse
- Monitor Telintel SMS Gateway HTTP API operational status and events

## Use cases

### Communications Operations

Use the Telintel SMS Gateway HTTP API to perform communications operations programmatically. The API provides 4 endpoints covering core functionality including sendsinglesms_messagedelivery, sendmasssms_notificationservice, deliveryreceipt_confirmdeliveryreceipt.

Example prompt: Call POST `/HttpSmppServiceTypeV2/HttpServiceType` to sendsinglesms_messagedelivery

### Automated Send Single SMS Management

Automate send single sms operations by combining multiple Telintel SMS Gateway HTTP API endpoints. Agents can sendmasssms_notificationservice and then deliveryreceipt_confirmdeliveryreceipt in a single workflow.

Example prompt: Call POST `/HttpMassSmppGatewayV2/HttpMassService` to sendmasssms_notificationservice, then verify the result

### AI Agent Integration via Jentic

AI agents discover and call Telintel SMS Gateway HTTP 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 none tokens manually.

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

## Key endpoints

| Method | Path | Description |
| --- | --- | --- |
| POST | `/HttpSmppServiceTypeV2/HttpServiceType` | SendSingleSms_messageDelivery |
| POST | `/HttpMassSmppGatewayV2/HttpMassService` | SendMassSms_notificationService |
| POST | `/Delivery` | DeliveryReceipt_confirmDeliveryReceipt |
| POST | `/MO` | ReceiveMessage_callbackResponse |

## Key resources

- **Send Single SMS** — The Send Single SMS API is designed to send a single SMS, the answer is synchronously.
- **Send Mass SMS** — The Send Mass SMS API is designed to be used when sending simultaneous transactions is not an option
- **Delivery Receipt** — Telintel will send a delivery receipt (where applicable) for each SMS submission. In order for Telin
- **Receive message** — If a short code or a long number have been purchased and inbound messages are required then a CallBa

## 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:** 34 / 100
- **Maturity:** Non-Ready
- **Dimensions:**
  - Foundational Compliance: 100 / 100
  - Developer Experience & Jentic Compatibility: 67 / 100
  - AI-Readiness & Agent Experience: 12 / 100
  - Agent Usability: 94 / 100
  - Security: 100 / 100
  - AI Discoverability: 100 / 100
- **View full report:** https://jentic.com/apis/smsapi.telintel.net/smsapi-telintel/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 Telintel SMS Gateway HTTP API by hand means posting to its SmppUtilsWeb endpoints, choosing between the plain HTTP port and the HTTPS port, and handling delivery and inbound callbacks yourself. Through Jentic you install once, import the Telintel SMS Gateway HTTP API from the API Directory, store the connection credentials once, and your agent calls it.
- **Permission scoping:** The Telintel SMS Gateway HTTP API takes its target in the request body rather than a resource id in the URL path, so limit the agent to the operations it needs, such as sending a single SMS or a mass send. You choose that set, so delivery and inbound handlers can be included or left out as you decide.
- **Credential handling:** Any credentials the Telintel SMS Gateway HTTP API needs 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 'send a single SMS' or 'send a mass SMS batch', and Jentic returns the matching Telintel SMS Gateway HTTP 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 Telintel SMS Gateway HTTP API use?

The Telintel SMS Gateway HTTP API uses no authentication. 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 sendsinglesms_messagedelivery with the Telintel SMS Gateway HTTP API?

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

### What are the rate limits for the Telintel SMS Gateway HTTP 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 sendsinglesms_messagedelivery through Jentic?

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

### How many endpoints does the Telintel SMS Gateway HTTP API have?

The Telintel SMS Gateway HTTP API exposes 4 endpoints covering send single sms, send mass sms, delivery receipt operations.

### Can I limit what my agent is allowed to do with the Telintel SMS Gateway HTTP API?

Yes. Because you run Jentic One yourself, your own rules decide which of the API's four operations and which credentials your agent may use. This API takes its target in the request body rather than a resource id in the URL path, so you scope the agent to just the operations it needs, such as sending a single SMS or a mass SMS send, and leave out the delivery-receipt and inbound-message handlers if you choose. The operator picks that set, and the agent can call nothing outside it.