SMS mailing

SMSC

SMSC’s tariff page lists an SMS 100 package at 773.00, while its API documentation sets limits on message text and SMS validity.

These terms matter to media buyers comparing messaging costs or planning timed communications; package applicability and destination coverage are questions to resolve before choosing a workflow.

Editorial review based on public sources, without hands-on testing; facts checked on 2026-10-31.

This page contains no partner link to this service.

Logo: Each logo belongs to its owner and appears here only to help identify the service.
Name: SMSC
Category: SMS mailing
Official site: smsc.ru · No link provided
Facts checked: 2026-10-31

Package Prices Meet API Limits

SMSC’s tariff and API pages list the following prices and technical conditions, checked on 2026-10-31.

Package: SMS 500, 3,825.00 (SMSC tariff page, checked 2026-10-31).
Package: SMS 1,000, 7,580.00 (SMSC tariff page, checked 2026-10-31).
Package: SMS 5,000, 37,530.00 (SMSC tariff page, checked 2026-10-31).
Maximum SMS validity period: 24 hours (SMSC API documentation, checked 2026-10-31).

Five Packages Carry Listed Prices

SMSC’s tariff page lists five named SMS packages with prices, checked on 2026-10-31.

SMS 100 — 773.00.
SMS 500 — 3,825.00.
SMS 1,000 — 7,580.00.
SMS 5,000 — 37,530.00.
SMS 10,000 — 74,360.00.

The diagram lists four SMS packages and their page-listed prices. — Package names and prices are from the provider's tariff page. Built from facts published on smsc.ru; checked 2026-10-31.

API Routes Name Several Interfaces

SMSC’s FAQ mentions HTTPS, SMPP connections, and the API; SMS can be sent by GET or POST to the listed HTTP endpoint.

The provider lists access through HTTP/HTTPS, SMTP, SMPP, SOAP, and OMS. These documented interfaces identify routes, but do not by themselves establish compatibility with a buyer’s existing systems.

The sequence shows the HTTP and REST endpoints documented for sending SMS. — The endpoints are documented by the provider. Built from facts published on smsc.ru; checked 2026-10-31.

Clarify the Sending Terms With Support

SMSC lists a support phone number, 8 (800) 700 7672, on its homepage, checked on 2026-10-31.

SMSC’s homepage also lists a contact email. Use the provider’s answers to establish how package pricing, sending conditions, and reporting fit the planned workflow.

Requests Can Carry Timing Options

SMSC documents sending SMS to its HTTP endpoint using GET or POST requests. Its API documentation also describes a JSON-based sending endpoint at /rest/send/.

For authentication, the API page lists an API key as an alternative to a login and password. The documentation also describes HLR queries for checking mobile numbers and scheduled delivery at a specified time.

Recurring SMS delivery is documented with period values from 0.1 to 720 hours. A sample booking-message template uses %w and %d placeholders. These options describe documented request capabilities, not a guarantee about message delivery.

The diagram lists the documented methods for accessing the SMSC API. — The provider lists these API access methods. Built from facts published on smsc.ru; checked 2026-10-31.

Documented Routes Offer Choice

SMSC lists API access through HTTP/HTTPS, SMTP, SMPP, SOAP, and OMS, giving buyers several documented interfaces to assess against their systems. The API documentation names an API key as an alternative credential to login and password details.

The documented options include HLR queries for mobile-number checks and scheduled SMS delivery at a specified time. These are useful distinctions to verify against the intended workflow before selecting a route.

Message and Attachment Caps Shape Use

SMSC’s API documentation sets limits on message text, SMS validity, and email attachments; the limits are not interchangeable.

The API accepts message text up to 1,000 characters, according to SMSC’s API documentation, checked 2026-10-31.
SMS validity is capped at 24 hours in the API documentation, checked 2026-10-31.
The same documentation limits email attachments to 20 files and 10 MB per file; this is an email attachment rule, not an established SMS attachment condition.

The package prices and API limits appear on separate pages, so confirm which conditions apply to the chosen package and route. Several other operating details are listed under What we could not confirm.

The diagram groups message, validity, and attachment limits documented by SMSC. — The attachment limit concerns email attachments in the cited API documentation. Built from facts published on smsc.ru; checked 2026-10-31.

Recurring Messages Suit Timed Workflows

SMSC’s documented scheduling and recurring-delivery options may suit workflows that need messages sent at a specified time or repeated at set intervals. A buyer considering either option should check how the requested timing relates to the intended message schedule.

The API also supports HLR queries for checking mobile numbers, which may be relevant when number checks are part of the workflow. That describes a documented function, not a conclusion about number status or eventual message delivery.

Compare by Message and API Terms

For SMS services in general, compare the pricing basis, destination and sender coverage, API methods, delivery reporting, restrictions, and support before choosing. Ask providers how those terms apply to the planned route and message type; the comparison is useful only when the conditions being compared are clear.

What we could not confirm

Rules and terms of use: applicable restrictions and conditions
Company details: legal entity, address, and history
Integrations: supported services and setup requirements
Additional tariff pages: package details and conditions
Destination coverage: countries and local sending conditions
Sender identification: permitted IDs and approval conditions
Delivery reports: available statuses and reporting method
Billing: currency, pricing basis, and balance application
Compliance: content rules and recipient-consent requirements

Questions About SMSC’s Published Terms

Which SMS package prices does SMSC list?

SMSC’s tariff page lists SMS 100 at 773.00, SMS 500 at 3,825.00, SMS 1,000 at 7,580.00, SMS 5,000 at 37,530.00, and SMS 10,000 at 74,360.00. The listed figures do not by themselves specify a per-message rate.

Which API endpoints and request methods are documented?

The API documentation says SMS can be sent to the listed HTTP endpoint using GET or POST requests.

What credential alternative does SMSC list?

SMSC’s API page lists an API key as an alternative to a login and password.

Which timing and number-check options are documented?

The API supports scheduled SMS delivery at a specified time, recurring SMS delivery, and HLR queries for checking mobile numbers. The recurring-delivery period values are from 0.1 to 720 hours, according to SMSC’s API documentation.

What limits does the API documentation state?

SMSC’s API documentation accepts message text up to 1,000 characters and states a maximum SMS validity period of 24 hours. It also limits email attachments to 20 files and 10 MB per file; that attachment condition concerns email.

Which support contacts does SMSC list?

SMSC’s homepage lists contact details. Ask support to clarify package applicability, sender and destination coverage, and delivery reporting before settling on a workflow.

Proceed After Terms Match the Workflow

Fits if… the documented API options align with the intended workflow and support clarifies package applicability, sender and destination coverage, and delivery reporting.

Probably not if… the workflow requires confirmed operating conditions before those points have been answered.

Main risk… treating the tariff-page package prices and API limits as a single set of terms when the pages do not connect them.

Sources

Public pages the facts above were taken from, with the date each was read.

smsc.ru/tariffschecked 2026-10-31
smsc.ru/api/httpchecked 2026-10-31
smsc.ru/faqchecked 2026-10-31
smsc.ruchecked 2026-10-31
smsc.ru/faq/161/kakovy-pravila-registratsii-shablonov-tranzaktsionnyh-i-servisnyh-soobscheniichecked 2026-10-31

How we put this page together

Editorial team of Affiliate Index. The editors at Affiliate Index wrote this page from the public sources listed above, which were read on 2026-10-31. Nobody tried the service in practice. If a source changes, the page is revised.

Last updated: 2026-10-31

Right of reply

Representatives of SMSC can contest this entry: write to us and attach evidence of the inaccuracy. We correct the entry or remove it once the refutation is documented. Entries are never removed or softened for payment.