SMS infrastructure for business-critical communication

Roha & Copita Telecom helps businesses route approved A2P SMS traffic through scalable messaging infrastructure — OTP delivery, transactional notifications, bulk customer campaigns, SMPP traffic and global SMS delivery for high-volume use cases.

How approved A2P traffic goes live

Built for regulated and high-volume messaging

Destination-based pricing for approved A2P traffic

Pricing depends on destination, traffic type, sender ID requirements, route quality and monthly volume. Current rates are available on request.

Compliance-first messaging

Roha & Copita Telecom supports legitimate A2P messaging. Traffic may be reviewed before production access, especially for aggregators, licensed gaming, regulated industries and high-volume routes.

Frequently asked questions

SMS API for Global Business Messaging

Send OTP, transactional alerts and customer notifications through a REST JSON SMS API.

The Roha & Copita Telecom SMS API helps enterprises, platforms and regulated businesses connect messaging directly to their applications. Use it to send verification codes, customer alerts, order updates, service notifications and business-critical SMS traffic.

From request to delivery report

Authorization: Bearer YOUR_API_TOKEN
Content-Type: application/json

{
  "to": "+447700900000",
  "from": "BrandName",
  "text": "Your verification code is 482913",
  "callback_url": "https://example.com/webhooks/sms-status"
}

{
  "message_id": "msg_123456789",
  "status": "accepted",
  "created_at": "2026-06-29T10:30:00Z"
}

Public API documentation is available as a preview. Production credentials are issued after account and traffic approval.

What makes a good SMS route

Not all SMS routes are equal. The platform routes A2P traffic only on carrier-grade connections — direct operator agreements or Tier-1 aggregator interconnects where applicable. Grey-route or SIM-farm traffic is prohibited and actively filtered at ingress.

API limits and advanced parameters

Ready to connect your application?

SMPP Gateway for High-Volume A2P SMS Traffic

Connect enterprise messaging systems, telecom platforms and aggregators through SMPP 3.4.

The Roha & Copita Telecom SMPP Gateway is designed for high-volume A2P senders that need persistent connectivity, protocol-level delivery receipts and structured traffic control.

Connection parameters

Bind types

submit_sm parameters

Key fields for outbound message submission. All mandatory fields must be present even when set to default values.

Long SMS — UDH vs SAR TLV

Messages exceeding one segment must be split and concatenated. Two methods are supported; SAR TLV is preferred for aggregator connections.

esm_class   = 0x40
data_coding = 0x00   ; GSM-7
short_message = \x05\x00\x03\xAB\x02\x01 + part1_text
                                ; ref=0xAB total=2 seq=1

sar_msg_ref_num    (0x020C) = 0x00AB  ; 16-bit ref
sar_total_segments (0x020E) = 0x02    ; 2 parts
sar_segment_seqnum (0x020F) = 0x01    ; this is part 1

Supported PDUs & delivery receipt format

id:1a2b3c4d sub:001 dlvrd:001
submit date:2406291402 done date:2406291403
stat:DELIVRD err:000 text:Your verification...

Window size & keep-alive

Standard SMPP command status

Connect high-volume traffic through SMPP

OTP and 2FA SMS Delivery Through API

Send verification codes for login, signup, payment confirmation and account security flows.

OTP and 2FA messages are time-sensitive. Roha & Copita Telecom helps businesses deliver verification codes through SMS API with delivery visibility, sender ID support and compliant routing.

Common OTP delivery issues

OTP delivery questions

Discuss your OTP traffic profile

Bulk SMS for Approved Business Campaigns

Send customer updates, operational notifications and approved campaigns through dashboard and SMPP.

Roha & Copita Telecom supports bulk SMS for legitimate business communication at virtually any scale. Whether you send a few thousand transactional alerts a day or push multi-million message campaigns across dozens of destinations, the same infrastructure routes every message through carrier-grade SMPP connections built for sustained high throughput.

Over a single SMPP 3.4 bind you can stream very large volumes in a continuous flow — tens of thousands of messages per second per session, with multiple binds running in parallel for even higher aggregate capacity. A campaign of half a million recipients is accepted, queued and dispatched in minutes rather than hours, while adaptive routing keeps delivery rates high and latency low across every leg of the journey.

Persistent connections, window-based concurrency, automatic retries and real-time delivery receipts mean your traffic moves fast and stays fully observable — from the first message to the last. You watch throughput, delivery quality and per-destination status update live, so large sends never turn into a black box.

From half a million numbers to delivered — in three screens

Upload your audience, write your message and hit send. The dashboard streams the whole campaign over SMPP in real time and hands you a delivery report the moment it finishes.

Plan your bulk SMS traffic

SMS Pricing and Europe-First Coverage

Destination-based SMS pricing for enterprises, aggregators and high-volume A2P traffic.

SMS rates depend on destination, route quality, traffic type, sender ID requirements and monthly volume. Current rates are available on request after traffic and destination review.

What affects the rate

Pricing questions

Request a destination-based quote

SMS API Documentation

REST JSON API for A2P SMS delivery. Bearer Token authentication, async delivery reports, webhook callbacks and full message lifecycle tracking.

Send your first message in 60 seconds

Replace YOUR_API_TOKEN with your production Bearer Token. Tokens are issued after traffic approval.

curl -X POST https://api.rocotele.com/v1/messages \
  -H "Authorization: Bearer YOUR_API_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Idempotency-Key: $(uuidgen)" \
  -d '{
    "to": "+447700900000",
    "from": "BrandName",
    "text": "Your verification code is 482913. Valid for 5 minutes. Do not share it.",
    "priority": "high",
    "validity_period": 5,
    "callback_url": "https://example.com/webhooks/dlr",
    "client_reference": "otp-user-58291"
  }'

import requests, uuid

response = requests.post(
    "https://api.rocotele.com/v1/messages",
    headers={
        "Authorization": "Bearer YOUR_API_TOKEN",
        "Content-Type": "application/json",
        "Idempotency-Key": str(uuid.uuid4()),
    },
    json={
        "to": "+447700900000",
        "from": "MyBrand",
        "text": "Your order #58291 has been dispatched. Track: example.com/track/58291",
        "callback_url": "https://example.com/webhooks/dlr",
        "client_reference": "order-58291",
    }
)
data = response.json()
print(data["message_id"], data["status"])

const response = await fetch('https://api.rocotele.com/v1/bulk/messages', {
  method: 'POST',
  headers: {
    'Authorization': 'Bearer YOUR_API_TOKEN',
    'Content-Type': 'application/json',
  },
  body: JSON.stringify({
    messages: [
      { to: '+447700900001', from: 'MyBrand', text: 'Flash sale ends tonight!', client_reference: 'c001' },
      { to: '+447700900002', from: 'MyBrand', text: 'Flash sale ends tonight!', client_reference: 'c002' },
    ],
    campaign_id: 'flash-sale-june',
    callback_url: 'https://example.com/webhooks/dlr',
  }),
});
const { batch_id, total } = await response.json();
console.log(`Batch ${batch_id} · ${total} messages accepted`);

$ch = curl_init('https://api.rocotele.com/v1/messages/msg_01J5KQ7N2P4RX8BVGW3T');
curl_setopt_array($ch, [
    CURLOPT_RETURNTRANSFER => true,
    CURLOPT_HTTPHEADER     => [
        'Authorization: Bearer YOUR_API_TOKEN',
        'Accept: application/json',
    ],
]);
$body   = curl_exec($ch);
$status = json_decode($body, true)['status']; // "delivered"
curl_close($ch);

Bearer Token

POST /v1/messages HTTP/1.1
Host: api.rocotele.com
Authorization: Bearer rct_live_xxxxxxxxxxxx
Content-Type: application/json
Idempotency-Key: 550e8400-e29b-41d4-a716-446655440000

{
  "error": "invalid_token",
  "message": "Bearer token is missing or invalid.",
  "request_id": "req_01J5KQ7N2P4RX8BVGW3T"
}

Message status lifecycle & webhooks

{
  "event": "message.delivered",
  "message_id": "msg_01J5KQ7N2P4RX8BVGW3T",
  "client_reference": "order-58291",
  "status": "delivered",
  "to": "+447700900000",
  "from": "BrandName",
  "parts": 1,
  "encoding": "gsm7",
  "error_code": null,
  "submitted_at": "2026-06-30T10:30:00.890Z",
  "delivered_at": "2026-06-30T10:30:02.114Z"
}

Character encoding & message parts

Throughput & retry guidance

HTTP/1.1 429 Too Many Requests
Retry-After: 3
X-RateLimit-Limit: 100
X-RateLimit-Remaining: 0
X-RateLimit-Reset: 1751285403

{
  "error": "rate_limited",
  "message": "Throughput limit exceeded.",
  "retry_after": 3
}

import time, random

def send_with_retry(payload, max_retries=5):
    delay = 1
    for attempt in range(max_retries):
        r = requests.post(URL, headers=HEADERS, json=payload)
        if r.status_code == 429:
            wait = int(r.headers.get("Retry-After", delay))
            jitter = random.uniform(0.8, 1.2)
            time.sleep(wait * jitter)
            delay = min(delay * 2, 60)
        else:
            return r
    raise Exception("Max retries exceeded")

Error codes reference

All errors return a JSON body with error, message and request_id fields. Log the request_id for support escalation.

SMS Compliance and Traffic Approval

A2P SMS traffic must follow sender ID, consent, destination and acceptable use requirements.

Roha & Copita Telecom supports legitimate A2P messaging. Production access may require traffic review, especially for aggregators, licensed gaming, regulated industries and high-volume destinations.

GDPR and platform security

Platform policies

Messaging Solutions for High-Volume and Regulated Businesses

SMS infrastructure for enterprise, telecom, aggregator and regulated messaging use cases.

Built for regulated and high-volume messaging

What every account includes

Find the right messaging solution

Contact Roha & Copita Telecom

Tell us about your traffic, destinations and integration requirements.

Acceptable Use Policy

Effective date: 1 January 2025. This policy governs all traffic sent through Roha & Copita Telecom infrastructure.

1. Purpose

Roha & Copita Telecom provides A2P SMS infrastructure — including SMS API and SMPP Gateway — for legitimate business messaging. This Acceptable Use Policy ("AUP") defines the conditions under which clients may access and use the platform. All clients must agree to this policy before receiving production credentials.

2. Permitted use cases

The platform may be used exclusively for the following categories of traffic:

3. Prohibited content and traffic

The following types of content and traffic are strictly prohibited on the platform:

4. Client responsibilities

Clients are solely responsible for:

• Obtaining and maintaining valid recipient consent in accordance with applicable law
• Ensuring message content complies with all destination-country regulations
• Providing accurate traffic descriptions during onboarding and review
• Maintaining suppression lists and honoring opt-out requests promptly
• Keeping sender ID registrations current in applicable countries
• Notifying Roha & Copita Telecom of any material change to traffic type, volume or destination

5. Enforcement

Violations of this policy may result in immediate traffic suspension, account termination and reporting to relevant authorities. Roha & Copita Telecom reserves the right to inspect traffic samples and request supporting documentation at any time.

6. Policy updates

This policy may be updated to reflect changes in applicable law, industry standards or platform capabilities. Continued use of the platform constitutes acceptance of the current version.

Anti-Spam Policy

Roha & Copita Telecom operates a zero-tolerance policy toward unsolicited, deceptive and abusive messaging.

1. Definition of spam

For the purposes of this policy, "spam" means any unsolicited, bulk or deceptive commercial message sent without the prior express consent of the recipient, or sent in violation of the recipient's opt-out request. Spam includes, but is not limited to, messages sent to purchased lists, harvested numbers, or recipients who have not engaged with the sender in a legitimate commercial context.

2. Consent requirements

Clients sending marketing or promotional messages must hold documented evidence of consent for each recipient. Acceptable consent mechanisms include:

• Opt-in at point of sale or registration — explicit checkbox or affirmative action where the recipient specifically agreed to receive SMS marketing
• Double opt-in — recipient confirmed consent via a reply SMS or link click after the initial sign-up
• Written or electronic consent forms — signed documentation stating the sender's brand and the type of messages to be received
• Existing customer relationship — for transactional messages related to a product or service the recipient purchased, where a reasonable expectation of communication exists

3. Opt-out and suppression

Every marketing or promotional message must include a clear and functional opt-out mechanism. Clients must:

4. Message content standards

All messages must meet the following content standards regardless of traffic type:

• The sender must be clearly identifiable from the sender ID or message body
• Messages must not contain deceptive, misleading or false information
• URLs embedded in messages must resolve to the sender's legitimate domain
• Messages must not impersonate another organization, brand, or government entity
• Message frequency must be proportionate to the nature of the consent given

5. Destination-specific rules

Many destinations impose additional anti-spam requirements beyond this policy. These may include time-of-day sending restrictions, mandatory sender ID registration, template pre-approval and local consent law requirements. Clients are responsible for compliance with all destination-specific rules. Roha & Copita Telecom may impose additional requirements on a per-destination basis.

6. Reporting spam

If you believe that Roha & Copita Telecom infrastructure is being misused to send you unsolicited messages, please contact us at compliance@rocotele.com with the message content, sender ID, timestamp and your phone number. We take abuse reports seriously and investigate every complaint.

Sender ID Rules

Sender ID availability and format depend on destination country rules. Some countries require registration or pre-approval before delivery is possible.

1. What is a Sender ID?

A Sender ID is the name or number that appears as the originator of an SMS message on the recipient's handset. Roha & Copita Telecom supports alphanumeric sender IDs (e.g., "MyBrand"), numeric long numbers and, where applicable, short codes. The type of sender ID that can be used depends on the destination country's mobile network operators and regulatory framework.

2. Sender ID formats

3. Registration requirements by region

Sender ID registration requirements vary significantly by country. The table below summarises the general requirements for key markets:

4. What you need to provide for registration

To register a sender ID on your behalf, Roha & Copita Telecom typically requires:

• Company legal name and registration documents
• Proof of brand ownership (trademark, domain registration, or equivalent)
• Company website URL
• Sample message text and use case description
• Target destination countries and estimated monthly volume
• Contact person with authority to sign the registration declaration

5. Sender ID restrictions

Clients must not use sender IDs that impersonate another company, brand or government entity. Sender IDs must reflect the actual sender's identity. Use of a sender ID that does not belong to the client, or that was not approved during registration, may result in immediate traffic suspension.

Traffic Approval

Production access to Roha & Copita Telecom requires traffic review. This page explains what to expect and how to prepare.

1. Why traffic approval is required

Roha & Copita Telecom routes traffic exclusively through compliant, high-quality paths. To protect network integrity and comply with operator agreements, all clients undergo a traffic review before production credentials are issued. This allows us to verify the traffic type, sender identity, use case legitimacy and destination fit before any messages are sent.

2. Traffic categories requiring review

The following traffic types always require full review before production access:

3. Approval process

4. Review timelines

5. Ongoing compliance

Approval is granted for the traffic profile submitted at onboarding. Any material change to traffic type, destination, volume, sender ID or content must be reported to Roha & Copita Telecom before the change is made. Sending traffic outside the approved parameters may result in suspension.

Data Protection

How Roha & Copita Telecom collects, processes, stores and protects personal data in connection with SMS delivery services.

1. Data controller

Roha & Copita Telecom acts as a data processor for the personal data of message recipients on behalf of its clients (data controllers). For the purpose of account management, billing and compliance, Roha & Copita Telecom also acts as a data controller for client contact information. This notice applies to both roles.

2. Data we process

3. Legal basis for processing

Processing is based on the following legal grounds under GDPR Article 6:

• Contract performance — processing client account data is necessary to deliver the agreed services
• Legal obligation — retention of certain records is required under applicable law and operator agreements
• Legitimate interest — traffic logging and delivery receipt processing are necessary for the technical operation of the SMS platform
• Controller instruction — recipient data is processed exclusively on documented instructions from the client as data controller

4. Data retention

5. Infrastructure and sub-processors

Roha & Copita Telecom uses the following infrastructure providers as sub-processors. All sub-processors are bound by GDPR-compliant data processing agreements:

6. Your rights

Under GDPR, data subjects have the following rights in relation to personal data we hold as a data controller:

• Right of access — request a copy of the personal data we hold about you
• Right to rectification — correct inaccurate or incomplete personal data
• Right to erasure — request deletion of personal data, subject to legal retention obligations
• Right to restriction — restrict processing in certain circumstances
• Right to object — object to processing based on legitimate interests

To exercise any of these rights, contact us at privacy@rocotele.com. We will respond within 30 days.

7. Data breach notification

In the event of a personal data breach that poses a risk to the rights and freedoms of individuals, Roha & Copita Telecom will notify the relevant supervisory authority within 72 hours. Affected clients will be notified without undue delay. Clients who are data controllers are responsible for notifying their own supervisory authority and data subjects where required.