Skip to main content
This section contains deprecated endpoints that will be removed on June 1, 2026. Please migrate to the new endpoints in the Messaging Channels section.

​
Why These Endpoints Are Deprecated

The original “Transactionals” API had several limitations:
  • ❌ Inconsistent naming and structure
  • ❌ Limited template management capabilities
  • ❌ No support for WhatsApp and other channels
  • ❌ Unclear separation between channels
  • ❌ Missing analytics and tracking features
The new Messaging Channels API addresses all these issues with:
  • ✅ Consistent structure across all channels
  • ✅ Better template management
  • ✅ Multi-channel support (Email, WhatsApp, SMS coming soon)
  • ✅ Enhanced analytics and stats
  • ✅ Improved error handling and validation

​
Migration Guide

​
Email Transactionals → Email Templates

Old endpoint (deprecated): 
POST /api/transactionals
New endpoint: 
POST /api/templates/email/send

​
Request Structure Comparison

{
  "uid": "unique_template_id",
  "recipient": "[email protected]",
  "customFields": {
    "name": "John Doe",
    "orderNumber": "12345"
  }
}
Key changes:
  • uid → templateId (more descriptive)
  • Template IDs now use tmpl_ prefix for clarity
  • Response includes more metadata

​
WhatsApp Migration

Old endpoint (deprecated): 
POST /api/transactionals/whatsapp/send
GET /api/transactionals/whatsapp/templates
New endpoints: 
POST /api/templates/whatsapp/send
GET /api/templates/whatsapp
The structure is largely the same, but with improved error messages and validation.

​
Migration Timeline

DateMilestone
November 2025New API released, legacy API deprecated
December 2025Migration guide published
March 2026Legacy API enters maintenance mode (bug fixes only)
May 2026Final migration warnings sent to all users
June 1, 2026Legacy API removed
You have until June 1, 2026 to migrate. After this date, the legacy endpoints will return 410 Gone errors.

​
How to Migrate

1

Audit Your Integration

Identify where you’re using the old endpoints:
# Search your codebase
grep -r "/api/transactionals" .
2

Update API Calls

Replace old endpoints with new ones:
  • /api/transactionals → /api/templates/email/send
  • /api/transactionals/whatsapp/send → /api/templates/whatsapp/send
  • /api/transactionals/whatsapp/templates → /api/templates/whatsapp
3

Update Request Payloads

Change uid to templateId in your requests:
// Before
{ uid: "abc123", recipient: "[email protected]" }

// After
{ templateId: "tmpl_abc123", recipient: "[email protected]" }
4

Test in Staging

Verify the new endpoints work as expected in your staging environment before deploying to production.
5

Deploy to Production

Once tested, deploy your changes to production.
6

Monitor & Verify

Check logs to ensure no errors and that messages are being delivered successfully.

​
Get Migration Help

Need assistance migrating?
We’re here to help! If you encounter any issues during migration, reach out to our support team.

​
Still Using Legacy Endpoints?

If you’re still using the deprecated endpoints below, you’ll see deprecation warnings in API responses: 
{
  "data": {
    /* your response */
  },
  "warning": {
    "message": "This endpoint is deprecated and will be removed on June 1, 2026",
    "deprecationDate": "2026-06-01",
    "migrateTo": "/api/templates/email/send",
    "docsUrl": "https://docs.minimo.it/api-reference/messaging-channels/email/send-template"
  }
}
Use these warnings to track which integrations need updating.