Trigger approved SMS or MMS messages from customer software.
Product detail · Supervised access
Connect business messaging to a defined software workflow.
Send and receive registered business messages through approved software workflows without exposing unrestricted carrier or platform access.
Best fit
For a real integration need—not general platform access.
- Customers with a defined custom integration that needs to send or receive business messages
- Software-triggered notifications, replies, delivery status, or other approved messaging workflows
- Teams prepared to involve Heritage in design, registration, development, testing, and ongoing access control
Approved capabilities
Messaging building blocks
Deliver inbound message events to an approved webhook workflow.
Process delivery-status events exposed by the selected implementation.
Restrict credentials, endpoints, and operations to the agreed scope.
Telephone-number provisioning is not included in the SMS API.
Provider-specific implementation
REST underneath. A controlled access path in front.
Current implementations use SkySwitch or Bandwidth. The selected provider, authentication method, permitted endpoints, webhook behavior, and credential handling are established during engineering review.
Customer software
Sends an approved request or receives an approved event.
Scoped access layer
Approved direct provider access or a Heritage-controlled gateway limits the integration to its authorized functions.
Messaging provider
The selected SkySwitch or Bandwidth implementation handles the carrier-facing messaging operation.
Engineering path
Define, register, constrain, then connect.
- 01
Define the workflow
Document message purpose, triggers, replies, expected volume, number type, data involved, and the people responsible.
- 02
Complete messaging registration
Heritage coordinates 10DLC registration. The customer supplies the required business information, consent practices, privacy policy, public website, and campaign details.
- 03
Choose the access architecture
Heritage confirms the appropriate SkySwitch or Bandwidth path and whether a restricted gateway is required for the approved workflow.
- 04
Implement with supervision
Heritage reviews authentication, endpoints, webhook destinations, errors, data handling, and access ownership. Paid development assistance is available.
- 05
Validate operational behavior
Test representative sends, replies, delivery events, failures, opt-out behavior, and applicable provider and carrier limits before routine use.
- 06
Maintain the approved scope
Provider changes, new endpoints, credential changes, volume changes, and workflow expansion require review.
10DLC and throughput
Campaign approval shapes the operating limits.
Heritage handles 10DLC registration and campaign coordination. Registration has fees and requires the standard campaign information and customer-facing prerequisites, including consent practices, a privacy policy, and a public website.
Throughput and rate limits depend on the selected provider, carrier requirements, and approved campaign type. This page does not promise a universal message rate or approval outcome.
Recorded boundaries
What this page does not promise
- The SMS API does not provide telephone-number provisioning
- Customers do not receive unrestricted access to Heritage carrier or platform accounts
- Authentication and available endpoints depend on the selected provider and approved architecture
- Throughput and rate limits depend on the selected provider, carrier requirements, and approved 10DLC campaign type
- Delivery, timing, carrier acceptance, and recipient handling are not guaranteed
Start with the workflow