Send Text Messages from Your Website via REST API (MTS Marketer)

An online store loses up to 30% of orders if confirmation doesn't arrive in time. Every second of delay costs customers. MTS Marketer solves this: its REST API provides access to MTS's subscriber base with 99.9% delivery guarantee and targeting by geolocation, gender, and interests. According to MTS Marketer official documentation, the average delivery time for transactional SMS is under 1 second, for marketing text messages up to 5 seconds. We have completed 50 integrations for e-commerce, banks, and logistics, handling over 10 million messages monthly. With correct setup, you get 90% of messages delivered within 3 seconds. We connect the service to your site—from simple notifications to complex marketing campaigns. MTS Marketer integration allows you to send text messages directly from your website, reducing costs by up to 30% through optimized routing and targeting. Text message sending from website is straightforward: below is an example of sending via PHP with Laravel.

How to Send SMS via MTS Marketer API?

// Authorization via Bearer token
$token = Http::post('https://api.mts-marketer.ru/v1/oauth/token', [
    'grant_type'    => 'client_credentials',
    'client_id'     => env('MTS_CLIENT_ID'),
    'client_secret' => env('MTS_CLIENT_SECRET')
])->json()['access_token'];

// Send text message
$response = Http::withToken($token)
    ->post('https://api.mts-marketer.ru/v1/sms/send', [
        'from'       => env('MTS_SENDER_NAME'),
        'to'         => [$phone],
        'text'       => "Confirmation code: {$code}",
        'is_test'    => false
    ]);

After sending, the API returns a message ID. You can get the delivery status using it:

$status = Http::withToken($token)
    ->get("https://api.mts-marketer.ru/v1/sms/status/{$messageId}")
    ->json();
// status: QUEUED | SENT | DELIVERED | FAILED

What Are Common Integration Errors?

Over the years of implementation, we have collected frequent issues:

• Incorrect number format. The number must be in international format: 7XXXXXXXXXX. Otherwise, the API returns INVALID_PHONE.
• Exceeding segment limits. If you send a marketing campaign to 100,000 numbers at once, make sure your tariff supports that volume (contact MTS support).
• Token expiration. The Bearer token lives for 1 hour. In production code, we implement automatic refresh via refresh-token.
• Missing alpha-name. Without a registered sender name (3–5 business days), the API blocks sending.
• Ignoring delivery statuses. Do not set up polling every 5 seconds—use webhooks to receive delivery notifications.

Reasons to separate transactional and marketing campaigns

MTS Marketer supports two modes, and mixing them up is not allowed. Transactional messages (OTP, order statuses) are delivered faster and do not require recipient consent under the contract. Marketing messages (promotions, news) are targeted based on MTS's subscriber base, but must comply with 152-FZ. Differences in characteristics:

Choosing the mode affects integration code: for transactional, set is_test => false, for marketing, pass segmentation parameters.

Setting up automatic token refresh

The Bearer token lives for 1 hour. For uninterrupted operation, implement automatic refresh using refresh-token. The process consists of three steps:

1. When receiving the token, save the refresh_token from the response.
2. 5 minutes before the current_token expires, send a request to /v1/oauth/refresh with the refresh_token.
3. Update the local storage with the new access_token and refresh_token. This prevents 401 Unauthorized errors in production.

Main MTS Marketer API methods

Ensuring integration security

Store client_secret in environment variables, do not pass it in code. Use HTTPS. Limit access rights—create a separate user with only text message sending permissions. Enable logging of all requests. Check delivery statuses via webhooks: configure an endpoint to receive notifications—this reduces polling load.

What's included in the work

Our integration is not just code insertion. We provide:

• Text message sending module—a dedicated class/service with support for transactional and marketing modes.
• Webhook handlers—receive delivery statuses and log them to a log file or database.
• Documentation—description of methods, integration scheme, administrator instructions.
• Testing in sandbox—check sending, error handling, limits.
• Training—show how to launch campaigns and read statistics.

Timeline and cost

Basic integration via REST API takes from 1 business day. If alpha-name registration is required (3–5 days for approval with MTS), add that time. Full cycle with testing and documentation takes up to a week. Typical integration cost starts at $500, and average monthly savings after integration reach $1,200. We always provide the final figure before starting work. No hidden fees. Through integration, you reduce text message costs by up to 30% by optimizing routes and targeting.

Integration steps

1. Obtain client_id and client_secret from your MTS Marketer personal account.
2. Register an alpha-name (sender name) with MTS (takes 3–5 days).
3. Implement token refresh mechanism as described above.
4. Write code to send transactional or marketing text messages via the API.
5. Set up webhooks to receive delivery statuses.
6. Test in sandbox environment.
7. Deploy to production and monitor.

Our team has extensive experience in SMS integration and has implemented over 50 projects for e-commerce, banks, and logistics. MTS Marketer delivers messages 2x faster than competitor platforms, ensuring stable delivery and SLA compliance. Contact us for a detailed assessment of your project. Request a consultation with an MTS Marketer integration engineer.

Email Campaign Integration: Why Does It Often Break?

We’ve observed that a trigger email sent 10 minutes after registration converts 4–5 times better than the same email sent after 24 hours. This isn’t a marketing myth—it’s mechanics: while the user is still warm, while they remember the context. But most integrations with email services are built like this: form submits → synchronous HTTP request to API → if the API is slow, the user waits 3 seconds → the email either goes out or doesn’t, nobody knows. In one project, we saw a 30% drop in conversion simply because the email service responded with 504 and Laravel’s queue driver wasn’t configured. Lost emails often hit customers silently – no log, no alert, just a missing order confirmation.

If you’re facing lost emails or spam folder issues, order an audit of your current integration – we’ll find bottlenecks within 2 days.

Providers and Their APIs

Unisender — a Russian provider popular in the SMB segment. REST API, simple. Adding a contact: importContacts, sending a transactional email: sendEmail. Important: for transactional emails (order confirmations, password resets), Unisender Go is a separate service with a different API and separate pricing. Mixing bulk and transactional mailings in one stream is bad for domain reputation. Unisender Go handles up to 1000 requests per second.

SendPulse — provides email, SMS, web push, Viber, and Telegram bots through a unified API. Convenient for projects requiring an omnichannel approach. Automation 360 is a visual chain builder; you can trigger automation via API events. The PHP SDK (sendpulse/rest-api-php-sdk) is maintained but updated irregularly – better to use Guzzle directly.

Mailchimp — a choice for international audiences and marketing teams accustomed to the Mailchimp ecosystem. Transactional email via Mandrill (a subsidiary service). Marketing API v3 for list, tag, and campaign management. Webhooks for opens, clicks, unsubscribes, bounces.

SMS. For Russia: SMSCenter, MTS Exolve, Devino Telecom, SMS Aero. Their APIs are similar: a send method with phone, message, sender parameters (sender name must be registered separately with the operator). One nuance: the sender name must be registered through the aggregator with a contract – otherwise SMS won’t be sent on MTS/MegaFon/Beeline networks.

How to Build an Integration That Doesn’t Lose Emails?

Separate Transactional and Marketing Streams

Transactional emails (order confirmations, password resets, delivery status) go through a dedicated sender domain or subdomain tx.example.com. Marketing campaigns go through mail.example.com or news.example.com. If a marketing campaign receives many spam complaints, it should not affect the reputation of the transactional stream. According to SendGrid documentation, transactional messages should be sent through a dedicated IP pool to prevent cross-contamination.

Queue and Retry

Any call to the email API goes through a queue (Laravel Queue, Bull, Celery). If Unisender returns a 503, the job retries after 5 minutes, then 15, then 60. After 5 failed attempts, it goes to a dead letter queue with an alert. The user already received their 200 OK and knows nothing about the issue. This approach reduces bounce rate on projects to 0.5%.

Example Laravel job:

public function handle(): void
{
    try {
        $response = Http::post(config('services.unisender.email_url'), $this->params);
        if ($response->failed()) {
            $this->release(300); // retry after 5 min
        }
    } catch (\Throwable $e) {
        $this->release(300);
    }
}

Templates

We store templates in code (Blade, Twig, React Email), not in the provider’s interface. Reasons: versioning via Git, browser preview without sending, testability. For complex templates with dynamic content — react-email with export to HTML via @react-email/render.

Validation and Consent

Before adding a contact to a list — double opt-in (confirmation email). Store the confirmation timestamp in your own database. Upon unsubscription — synchronously unsubscribe both at the provider and in your database. Ignoring webhook unsubscriptions is a direct path to account suspension at the provider. All processes comply with Федеральный закон № 152-ФЗ «О персональных данных».

Deliverability Monitoring and DKIM Setup

Connect provider webhooks for events: bounce (hard and soft), spam_complaint, unsubscribe. Hard bounce — immediately mark the email as invalid in your database, stop sending. Soft bounce 3 times in a row — same. Metrics: open rate, click rate, bounce rate, unsubscribe rate — review at least once a week. Our certified engineers configure alerts in Grafana/Prometheus.

DKIM configuration steps:

1. Generate a key pair (e.g., openssl genrsa -out private.key 2048).
2. Publish the public key in DNS as a TXT record for the selector (e.g., mail._domainkey.tx.example.com).
3. Provide the selector to the provider (SendGrid, Mailgun, Unisender).
4. Verify with dig TXT mail._domainkey.tx.example.com.

SPF, DKIM, DMARC must be configured separately for each stream. We use subdomains with different DNS records.

Why Is It Important to Separate Streams?

If you send a marketing campaign from the same domain as transactional emails and receive spam complaints, you risk getting the domain blocked — and users will stop receiving even order confirmations. SPF, DKIM, DMARC (Sender Policy Framework, DomainKeys Identified Mail, Domain‑based Message Authentication, Reporting and Conformance) must be configured separately for each stream. In one project, a marketing blast with 12% spam complaints blocked the transactional domain for 48 hours — we had to re‑authenticate with Google and Yandex.

What Does the Integration Scope Include?

• Audit of current communication streams and domain reputation (SPF, DKIM, DMARC)
• Provider and schema selection: transactional vs marketing traffic
• Configuration of SPF, DKIM, DMARC DNS records
• Development of email templates (HTML + dynamic content)
• Backend integration via queues and API
• Webhook setup for deliverability and complaints
• Operations documentation and team training
• Deliverability guarantee and post‑launch support

We deliver production‑ready documentation, access to monitoring dashboards, and a handover session with your engineers. Our certified engineers provide a 30‑day post‑launch health check guarantee.

Timelines and Cost

Cost is calculated individually after audit. We provide turnkey service: from analysis to production monitoring. Contact us for a free engineer consultation — we’ll evaluate your project and give accurate timelines. Over 7 years of experience in email service integration, 50+ projects implemented. Order a free audit of your current integration and receive a report with recommendations and estimated savings.