REST API v3 and TNZ MCP Client Now Available
Upgrade to TNZ REST API v3.00 for simpler requests, expanded messaging APIs and workflow automation, plus connect AI tools with the TNZ MCP Client.
– 17 Jul, 2026
REST API v3.00 and the TNZ MCP Client
Upgrade your TNZ integration with simpler request structures, more communication channels, workflow automation, and a new way to connect AI tools to TNZ messaging.
Explore REST API v3.00 → Explore the TNZ MCP Client →Latest API release
v3.00
Built for cleaner integrations
OpenAPI 3.1 specification
Flattened message payloads
Expanded APIs and workflow support
Build and maintain message requests without the MessageData object.
Work with contacts, opt-outs, partners, WhatsApp, RCS, and more.
Trigger multi-step TNZ workflows directly from your application.
Use the TNZ MCP Client to add messaging capabilities to AI tools and agents.
A practical upgrade for v2.04 integrations
REST API v3.00 keeps the familiar TNZ messaging model while making everyday requests easier to construct. The most visible change is a flatter payload: message fields now sit in the primary object, so your integration no longer needs to wrap them in MessageData. The release also brings more TNZ services into one modern API, including improved Address Book API, Opt-Out API, WhatsApp and RCS.
Simpler requests, with less code to manage
In v2.04, message content and options are nested inside MessageData. In v3.00, fields such as Message and Destination can be supplied at the root level. That makes payloads easier to read, generate, validate, and troubleshoot.
Nested message data
{
"MessageData": {
"Message": "Your appointment is tomorrow",
"Destinations": [
{ "Recipient": "+6421000001" }
]
}
}
One clear request object
{
"Message": "Your appointment is tomorrow",
"Destination": "+6421000001"
}
These examples show the structural change only. Refer to the v3.00 documentation for the complete request schema and current field requirements.
Do more through one API
Version 3.00 extends the range of TNZ services your applications can use. Existing API users can move beyond individual message sends and connect more of their communication operations.
Address Book
Create, update, find, and organise contacts and groups, then send to saved contacts from your integration.
Opt-Out and Partner APIs
Bring opt-out management and relevant partner functions into your connected applications.
WhatsApp and RCS
Use newly published APIs for richer messaging channels alongside TNZ's established SMS, email, voice, and fax services.
Workflow automation
Start a multi-step workflow with a WorkflowTemplateID, giving your application a simple way to trigger more complete communication journeys.
Use the published specification to simplify setup in OpenAPI- and Swagger-compatible development tools, generate clients, or bring the API into your preferred testing workflow.
Give AI tools access to TNZ messaging
The TNZ MCP Client connects compatible AI tools and agents with TNZ services. It runs on your machine and passes the requests needed for delivery to TNZ, giving your AI workflows a direct route to real communication channels.
Set up the TNZ MCP Client →WHAT DOES MCP ENABLE?
Send SMS, email, and voice messages
Check delivery outcomes and replies
Manage Address Book contacts and groups
Act on communication results
The REST API change log records the additions, removals, renamed fields, and deprecations included in v3.00: Change Log
Start building with REST API v3.00
Review the new request structure, identify the changes relevant to your v2.04 integration, and use the updated documentation to plan and test your upgrade.
Open the v3.00 documentation → Review the API change log → Talk to the TNZ team →Topics: News