Skip to main content
This guide covers core Messaging API concepts, throughput limits, message expiry, and data logging.

​
Overview

Plivo’s Messaging API enables SMS and MMS messaging to 200+ countries with:
  • Programmable SMS/MMS via REST API
  • High throughput delivery
  • Delivery receipts and callbacks
  • Message logging and analytics

​
Messages Per Second (MPS)

MPS limits control how fast your account can send messages.

​
Default Limits

TypeDefault MPS
SMS5 MPS
MMS0.25 MPS
View your allocated MPS at SMS > Overview in the console.

​
US Throughput by Number Type

Number TypeSMS ThroughputMMS ThroughputDaily Limit
Long Code (Unregistered)1 msg/sec1 msg/sec2,000/day
Long Code (10DLC Low)0.2-0.75 msg/secVariesVaries
Long Code (10DLC Standard)3.75-15 msg/secVariesVaries
Toll-Free (Verified)25 msg/sec2 msg/secNo limit
Short Code100+ msg/secNot supportedNo limit

​
Canada Throughput

Number TypeSMSMMS
Long Code15/minute15/minute
Toll-Free25/second2/second
Short Code10/secondNot supported
Note: Verify toll-free numbers to avoid sending limits.

​
Message Expiry

Messages remaining in queue after 3 hours expire automatically.

​
What Happens

  • Message marked as “failed”
  • Error code: 420
  • No charge applied

​
Why Messages Expire

  • Carrier delays or congestion
  • Invalid destination number
  • Network issues

​
Data Logging Preferences

Control how Plivo stores your message data.

​
Options

SettingDestination NumberMessage Content
Store Both (Default)StoredStored
Store Number OnlyStoredNot stored
Store Content OnlyNot storedStored
Store NeitherNot storedNot stored

​
Configure via API

Set the log parameter in the Send Message API.

​
Message Types

​
Promotional vs Transactional

TypePurposeExamples
PromotionalMarketing, salesOffers, discounts, advertisements
TransactionalEssential informationOTPs, order confirmations, alerts
Different countries have varying regulations for each type.

​
Fraud Prevention

Plivo provides multiple fraud protection layers:

​
Geo Permissions

Restrict messaging to specific countries:
  1. Navigate to SMS > Settings > Geo Permissions
  2. Enable only required destination countries
  3. Set messaging thresholds per country

​
Unusual Traffic Alerts

Plivo monitors for suspicious patterns:
  • Sudden traffic spikes
  • Unusual destinations
  • Potential account takeover
You’ll receive alerts via email when anomalies are detected.

​
Monthly Limits

Set spending caps to prevent runaway costs from fraud.

​
Export Message Detail Records (MDR)

​
Via Console

  1. Navigate to SMS > Logs
  2. Click Filter Logs to refine
  3. Select records to export
  4. Click Export
Small exports download directly; large exports are emailed.

​
Via API

Use the Message API to retrieve records programmatically.

​
Line Breaks in Messages

Use \n for line breaks: 
curl -X POST "https://api.plivo.com/v1/Account/{auth_id}/Message/" \
  -u "{auth_id}:{auth_token}" \
  -H "Content-Type: application/json" \
  -d '{
    "src": "14151234567",
    "dst": "14157654321",
    "text": "Line 1\nLine 2\nLine 3"
  }'

​
Country Coverage

DirectionCoverage
Outbound SMS200+ countries
Inbound SMSUS, Canada, UK, Australia, France, Germany, Netherlands, Sweden, Austria, Belgium
See Plivo Coverage for details.

​
Compliance Standards

All messaging must follow:

​
Prohibited Content

  • Unsolicited spam
  • Fraudulent or deceptive content
  • Violence, hate speech, obscenity
  • Illegal substances promotion
See Messaging Compliance for details.

​
Integrations

​
Bitrix24

  1. Install Plivo from Bitrix24 Marketplace
  2. Enter Auth ID, Auth Token, and sender ID
  3. Click Test SMS to validate