Reference implementation and operations answers for Apeiron SMS/MMS messaging. For commercial updates and country-level rate detail, contact sales.
Core topics for day-to-day SMS program design and operation.
Inbound messaging is available on enabled long code, toll-free, and shortcode numbers. Messages can be consumed in Dashboard, delivered via webhook/API callback, or routed to notification profiles.
A long code is a standard 10-digit number (local DID or TFN in NANP contexts) used for two-way messaging programs with throughput and compliance limits based on carrier policy.
A short code is a 5- or 6-digit number typically used for higher-throughput programs. Short code approvals involve carrier/registry review and usually require lead time before production use.
Long code throughput is carrier-regulated. If your use case requires higher sends-per-second, coordinate with Apeiron to select an appropriate number and campaign model.
Use normalized destination formats as recommended by Apeiron for your program design. For NANP traffic, 1+10 digit formatting is commonly used in outbound workflows.
Operational notes for regional messaging support and integration patterns.
Inbound number support depends on number type and destination market. Contact Apeiron for current country-specific availability.
Outbound messaging supports broad global destinations. For active rate and route policy details, request a current commercial review.
Yes. API-based retrieval workflows are supported in addition to push notifications, depending on your integration design and operational preference.
Apeiron can review number strategy, compliance path, and integration design before launch.