Smsapi Telintel Telintel SMS Gateway HTTP API
★ Only Publicly Available OpenAPI DocumentCommunicationsSms Messagingnone4 EndpointsREST
For Agents
Programmatically sendsinglesms_messagedelivery, sendmasssms_notificationservice. Covers 4 operations.
Use for: I need to sendsinglesms_messagedelivery, I want to sendmasssms_notificationservice, Search for deliveryreceipt_confirmdeliveryreceipt, Find all receivemessage_callbackresponse
Not supported: Does not handle payments, crm, or developer tools - use for communications only.
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.
Install Jentic One Beta
Connect the Telintel SMS Gateway HTTP API to your agent
Jentic One is a self-hosted execution layer for AI agents. It lets your agent call the Telintel SMS Gateway HTTP API, or any other public or private API you need. You set the rules, the agent never sees your credentials, and every call is logged.
Two steps, two machines. Install the instance in a safe environment, then register your agent from wherever it runs.
1
Step 1: Jentic One Host machine
# On the machine that will host your Jentic One instance:
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsmsapi.telintel.net%2Fsmsapi-telintel" | sh2
Step 2: Agent machine
# On the machine where your agent runs (keep this separate from the instance):
curl -fsSL "https://jentic.com/install.sh?src=apis&api=%2Fapis%2Fsmsapi.telintel.net%2Fsmsapi-telintel" | sh
jentic register # connects your agent to your Jentic One instanceJentic One is in public beta. The setup above keeps your agent separate from the instance, which is what you want before using real credentials: an agent running as the same OS user as Jentic One can read its stored keys directly. Just evaluating? A single local install is fine to start. See the secure deployment guide for the tiers.
Capabilities
What an agent can do with Telintel SMS Gateway HTTP API.
SendSingleSms_messageDelivery
SendMassSms_notificationService
DeliveryReceipt_confirmDeliveryReceipt
ReceiveMessage_callbackResponse
Monitor Telintel SMS Gateway HTTP API operational status and events
Use Cases
Patterns agents use Telintel SMS Gateway HTTP API for, with concrete tasks.
★ 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.
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.
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.
Search Jentic for 'sendsinglesms_messagedelivery', load the operation schema, and execute with Jentic-managed credentials
Key Endpoints
4 endpoints — this service is intended for live traffic, it is scoped for notification systems.
METHOD
PATH
DESCRIPTION
POST
/HttpSmppServiceTypeV2/HttpServiceType
SendSingleSms_messageDelivery
POST
/HttpMassSmppGatewayV2/HttpMassService
SendMassSms_notificationService
POST
/Delivery
DeliveryReceipt_confirmDeliveryReceipt
POST
/MO
ReceiveMessage_callbackResponse
POST
/HttpSmppServiceTypeV2/HttpServiceType
SendSingleSms_messageDelivery
POST
/HttpMassSmppGatewayV2/HttpMassService
SendMassSms_notificationService
POST
/Delivery
DeliveryReceipt_confirmDeliveryReceipt
POST
/MO
ReceiveMessage_callbackResponse
Why Jentic?
What agents get from Jentic-routed access to this vendor.
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 isolation
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.
Intent-based discovery
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
Alternatives and complements available in the Jentic catalogue.
FAQs
Specific to using Telintel SMS Gateway HTTP API through Jentic.
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.
GET STARTED