Send an SMS or MMS notification directly without templates
POST /sms
Authorizations
Section titled “Authorizations ”Request Body required
Section titled “Request Body required ”Request body for POST /sms (send SMS or MMS without a template).
object
The notification type to send.
The phone number of the recipient.
The message of the SMS or MMS notification. Optional when mediaUrls is provided.
Public HTTPS URLs of media to attach (MMS).
The ISO 8601 datetime to schedule the SMS notification.
Override the sender phone number. Must be a dedicated number on your Pingram account.
Responses
Section titled “ Responses ”Successful response
Success response for POST /sms.
object
Error response for POST /sms.
object
Error details for SMS send failures.
object
Machine-readable error code.
Human-readable error message.
Actionable hint for fixing the error.
Provider that rejected the message (e.g. ‘telnyx’).
Provider-specific error code.
Bad Request - validation errors, invalid input
Standard error response for API errors.
object
Unique tracking ID for the request.
Structured error details for API error responses.
object
Machine-readable error code.
Human-readable error message.
Actionable hint for fixing the error.
Provider that caused the error (e.g. telnyx, ses).
Provider-specific error code.
Unauthorized
Payment Required - usage limits exceeded
Standard error response for API errors.
object
Unique tracking ID for the request.
Structured error details for API error responses.
object
Machine-readable error code.
Human-readable error message.
Actionable hint for fixing the error.
Provider that caused the error (e.g. telnyx, ses).
Provider-specific error code.
Internal Server Error
Bad Gateway - provider error
Standard error response for API errors.
object
Unique tracking ID for the request.
Structured error details for API error responses.
object
Machine-readable error code.
Human-readable error message.
Actionable hint for fixing the error.
Provider that caused the error (e.g. telnyx, ses).
Provider-specific error code.