Developers
TXTPro messaging API overview
The TXTPro messaging APIs let your application, CRM or backend send SMS, RCS, WhatsApp and voice messages over HTTPS, receive a message ID for each request, and get delivery and interaction updates back through webhooks or status retrieval.
How does the messaging API work?
- Your server authenticates with the API credentials issued to your account during onboarding.
- It sends an HTTPS request with the recipient, the channel and the channel-specific details: for SMS the DLT-registered header and template ID; for WhatsApp an approved template name; for RCS your verified agent and rich content; for voice the approved audio or IVR flow.
- The API validates the request and returns a message ID, which your system stores next to its own reference.
- Delivery and interaction events are reported back later, by webhook to your callback URL or by status retrieval, depending on the options available for your account.
Acceptance by the API means the request was valid and queued; it is not a delivery confirmation. Delivery depends on operators, platforms and the recipient’s device.
What each channel needs in an API request
| Channel | Typical request details | Prerequisites |
|---|---|---|
| Bulk SMS | Recipient, sender header, DLT template ID, template variables | Principal Entity, header and template registered on DLT |
| RCS | Recipient, agent, text or rich card content, suggestions | Verified and launched RCS agent |
| Recipient, approved template name and parameters, or a session reply | WhatsApp Business Account, approved templates, opt-in | |
| Voice | Recipient, approved audio or IVR flow, caller ID where applicable | Approved content and campaign setup |
Exact parameter names, formats and limits are defined in the API documentation shared with customers. Read How Messaging APIs Work for a generic explanation of request structure.
Authentication and credentials
- API credentials are issued per account during onboarding. The authentication method is described in the documentation you receive.
- Keep credentials on your server, in environment variables or a secrets manager. Never put them in mobile apps, browser code or source control.
- Use separate credentials for testing and production where available, and rotate them if they may have been exposed.
Delivery reports and webhooks
Status updates arrive asynchronously. A webhook pushes each event to your callback URL as it happens; polling asks the API for status on a schedule. The webhook integration hub explains SMS, RCS, WhatsApp and voice events, an illustrative payload and the ten-step integration process.
Channel guides cover SMS delivery report webhooks, RCS, WhatsApp and voice events. Runnable receivers are in the Node.js and Python guides, and the webhook security guide covers signatures, replay protection and safe logging.
Platforms with an SMPP client can use an SMPP v3.4 account instead of the HTTP API. Over SMPP, delivery receipts arrive as deliver_sm on the session rather than as webhooks; the SMPP integration guide and SMPP vs HTTP SMS API explain the differences.
Errors, retries and idempotency
- Treat validation errors (4xx) as permanent: fix the request rather than retrying it.
- Retry network errors and server errors (5xx) with exponential backoff and a maximum number of attempts.
- Attach your own reference to each send so a retried request does not create a duplicate message, where the API supports a client reference or idempotency key.
- Respect rate limits and spread large campaigns over time.
Getting the API documentation
TXTPro does not publish a public API reference on this website. The technical documentation, including endpoints, authentication, parameters, status values and webhook formats, is shared with customers during onboarding, along with guidance for testing before going live.
Conceptual flow
From API request to your CRM
Step 1
Customer sends API request
Your system submits a message and stores the returned message ID.
Step 2
Messaging platform
The operator, RCS platform, WhatsApp or voice network handles delivery.
Step 3
Status / event
A delivery status or customer interaction is recorded for the message.
Step 4
Webhook callback
The event is sent as an HTTPS POST to your callback URL.
Step 5
Customer application
Your CRM or application matches the message ID and updates the record.
FAQs
API FAQs
Can’t find your answer? Contact our team.
Where can I find the TXTPro API documentation?
The API documentation is shared with customers during onboarding rather than published publicly. Use the Request API Documentation button on this page and our team will follow up.
Which programming languages can I use with the TXTPro API?
Any language that can make HTTPS requests and parse JSON, such as Node.js, Python, PHP, Java or .NET, can integrate with an HTTP messaging API.
Do I need to build a webhook endpoint?
Only if you want delivery and interaction events pushed to your system in near real time. Teams sending from the web panel, or with low volumes, may not need one. The options for your account are confirmed during onboarding.
Related resources
Plan your API and webhook integration
Tell us which channels and events you need and where they should go. Our team will explain the integration options for your account and share the technical documentation during onboarding.
Prefer to call? +91 90304 02858 · Email info@txtpro.in
