Concepts
MassAccess API allows sending messages to clients via popular messengers, tracking delivery statuses, and managing phone numbers — all through a single interface.
Architecture
Your server sends a request to the MassAccess API. After key verification and validation, a 202 Accepted response with event_id and state new is returned immediately. MassAccess then asynchronously delivers the message to the user and sends a webhook notification to your server with the delivery result.
Basic Concepts
Bots
A bot is a message delivery channel. Each bot is tied to a specific messenger (Telegram, MAX) and has a unique token.
Clients
A client is a message recipient identified by phone number. A client can be bound to multiple bots.
Webhooks
Delivery status webhooks are sent to your server via HTTP POST requests. You receive events in real time.
Message Lifecycle
| Code | Description |
|---|---|
| new | Message created, not yet processed |
| processing | Message is being processed by delivery system |
| sent | Message has been sent to messenger |
| failed | Message delivery failed |
Phone Number Format
All phone numbers must be 11 digits, matching the pattern ^\d{11}$. Example: 12345678901.
Service Types
| Code | Description |
|---|---|
| telegram | Telegram messenger |
| max | MAX corporate messenger |
Webhook Retry Policy
MassAccess retries failed webhook deliveries with exponential backoff: 1s, 5s, 25s, 125s, 625s (up to 5 attempts). Your server must return HTTP 200 to acknowledge receipt.
Rate Limiting
API requests are rate-limited per API key. When the limit is exceeded, the API returns HTTP 429 with a Retry-After header. Current limits: 100 requests per second per API key.