Submit an outbound SMS with a POST /api/v1/sms request. The documented REST endpoint uses Bearer token authentication.
Retrieve a paginated list of SMS messages sent from your account with GET /api/v1/sms.
Use GET /api/v1/sms/:id to retrieve information about a specific message, including status, source and destination, timestamps, cost and segment count.
Incoming messages to supported SMS-enabled numbers can be relayed to your endpoint through a configured webhook.
Tell us where you need to send, what type of messages you’re sending and your expected volume. Requirements vary by destination and traffic type.
Create your integration using the documented SMS endpoints and authenticate requests with your API token.
Your software submits SMS requests through the API. You can then retrieve sent messages and check the available details for individual messages.
Trigger one-time codes, login verification and account-recovery messages from your application where supported.
Send order updates, appointment reminders, service notifications and account alerts when an event occurs in your system.
Add SMS to an existing communications platform, CRM or contact-center workflow alongside voice.
Add SMS connectivity to a communications product without building the underlying telecom relationships yourself.
Use your own application to manage recipients and sending logic, then submit messages through the API.
Inbound SMS works differently from outbound API sending.
With a supported SMS-enabled didlogic number, incoming messages can be relayed to an endpoint you configure through webhooks. This lets your application process replies and other incoming SMS automatically.
SMS-enabled number availability depends on the country and number type.
Outbound SMS is priced by destination and billed in message segments. Your applicable rate can also depend on the traffic, sender setup, volume and available route.
A standard GSM-7 message contains up to 160 characters in a single segment. Unicode messages contain up to 70 characters. Longer messages can use multiple billable segments.
Customers rely on didlogic for global telecom services across markets. Here’s what they say about working with us, from setup and support to service reliability.
An SMS API lets software send and work with text messages programmatically.
The didlogic REST API provides endpoints for sending SMS, listing messages sent from your account and retrieving details about an individual message.
You can submit outbound SMS, retrieve a paginated list of sent messages and request details for an individual message.
For inbound SMS, supported SMS-enabled numbers can relay incoming messages to your endpoint through webhooks.
The documented SMS endpoints use Bearer token authentication.
You can build high-volume sending through the API. Your application manages the recipient list and sending logic and submits messages to the didlogic API.
didlogic does not provide a portal-based campaign builder for uploading a contact database and launching a bulk campaign.
The message-details endpoint returns the available delivery status and timestamps for an individual SMS. It also returns the source and destination, message content, cost and segment count.
Yes, with supported SMS-enabled numbers. Incoming SMS can be relayed to your endpoint through a configured webhook.
OTP, verification and transactional messages are supported A2P use cases, subject to the requirements and available routes for the destination.
Pricing depends on the destination and the number of SMS segments sent. Traffic type, sender setup, volume and available route can also affect the applicable rate.
Connect SMS to your application