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.