Service notification API for business

Keep your customers informed when it matters

Send order statuses, reminders, verification codes, and other service notifications through Telegram, MAX, and other connected channels via a unified API

Connect your company’s own Telegram and MAX bots

Recipients first start the bot and share their contact

On company registration

500

Free messages to get started

No usage expiration

then

RUB 0.59

per message

No subscription fee

Automate and simplify communication with your customers

One API for product and marketing notifications, security flows, support, and internal operations

Order and service statuses

Notify your customers when an order, request, or service state changes

Reminders

Send scheduled reminders through your customer's connected messengers

Support notifications

Deliver important support updates through channels available to your customers

Verification codes

Send your customers one-time codes to confirm sign-ins and operations

Personalized offers

Keep connected customers informed about relevant offers, promotions, bonuses, and new opportunities

Security

Alert customers about account sign-ins, data changes, and suspicious activity

From company registration to message delivery status

Connect in a few simple steps and reliably track the outcome of every message sent to your customers

  1. 01

    Register the company

    Create an account and get access to the MassAccess API

  2. 02

    Connect an available channel

    In the dashboard, connect and configure the bot you created using the visual scenario builder

  3. 03

    Register the recipient

    Your customer opens the bot via a link or QR code and shares their contact according to the scenario

  4. 04

    Send and track

    Your service sends an API request with the customer's phone number and message text, then receives webhooks about the message delivery status

Current channels on one platform

Telegram and MAX messengers are currently available. The unified API contract is designed to support other messengers and SMS. As the platform evolves, communication channels will be added automatically without requiring additional integration

Telegram

Connect a Telegram bot created and configured through the dedicated BotFather bot

Connect a Telegram bot

Choose where the application services run

The MassAccess platform is available in two deployment options: SaaS and On-premise. The same per-message price applies regardless of the option you choose

MassAccess SaaS

MassAccess operates all platform services. Your team connects and configures bots and integrates the API into your product services

On-premise package

Run the supplied platform application services in your infrastructure. Cloud billing is used to bill the On-premise package

Explore on-premise

One integration for all channels

Integrate MassAccess once and use the available communication channels through a unified API. MassAccess handles the integration specifics for each channel.

When new channels become available, your product's core integration with MassAccess remains unchanged.

A customer's phone number alone is not enough to start a conversation with the bot. First, the customer must register their contact through your bot according to its flow. You can then send messages to the bot using the customer's phone number
curl -X POST https://massaccess.net/api/v1/send \
  -H "X-API-Key: YOUR_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"phone_number":"01234567890","message":"Order ready"}'

Frequently asked questions

Can I message any phone number?

No. The recipient must first open your company bot, start its flow, and share their contact.

Is on-premise fully offline?

No. It requires outbound access to MassAccess for licensing, metering, and cloud billing.

Will new channels require integration changes?

Channel setup differs, but your service uses the unified MassAccess API. New messengers and SMS will be added as adapters to the same contract.

Connect company channels to one API

Create an account, connect a test bot, register a test customer, and verify the complete message sending status flow