Skip to content

Postback notification codes

This document details the postback notification codes for MMS MT and MMS MO notifications.

MMS MT postback codes

CodeStatusDescription
N101SentNotification that MMS was sent/processing started.
N102DeliveredNotification that MMS delivery status was updated or delivered. Carrier delivery receipts may not be available for all carriers.
N103ExpiredNotification that MMS expired.
E101FailedSending failure. Impossible to send MMS.
E102Rejected / UnrecognisedMMS delivery was not successful or destination/content was rejected/unrecognized.
N003Transcoding successfulSaved MMS transcoding completed and template is available.
E002Transcoding failedEncoding of MMS audio failed for savemms.
E003Transcoding failedEncoding of MMS video failed for savemms.
E004Transcoding failedEncoding of MMS image failed for savemms.
N013Transcoding successful and sending triggeredTranscoding completed and send processing was triggered.
E011Content validation failedContent validation failed.
E012Transcoding failedEncoding of MMS audio failed for sendmms; sending not triggered.
E013Transcoding failedEncoding of MMS video failed for sendmms; sending not triggered.
E202Fallback SMS delivery failureMMS as SMS delivery was not successful.
E999Queue processing errorPost message sending queue processing error.
N202Delivered as SMSNotification that MMS was delivered as fallback SMS.

MMS MO postback codes

CodeStatusDescription
N401MMS MO receivedInbound MMS received successfully.

MMS MT postback fields

FieldDescription
originMMS_MT.
codePostback notification code.
sent-asMMS if sent/delivered as MMS; SMS if delivered as fallback SMS.
statusTransaction status such as Sent, Delivered, Failed, Rejected, or Expired.
status-detailsDetailed status text.
toDestination phone number with country code.
fromSender number.
timestampTimestamp for the MMS MT transaction.
tracking-idTracking ID returned in the API response.
client-referenceCustomer transaction ID passed in the request.
mms-idMMS template ID when applicable.
handsetHandset profile returned inside delivery receipt when provided.
content-typeContent type when applicable.
content-nameContent file URL or object name when applicable.
error-infoError detail for failure scenarios.

Example: N101 MMS sent

{
  "origin": "MMS_MT",
  "code": "N101",
  "sent-as": "MMS",
  "status": "Sent",
  "status-details": "Message Sent",
  "to": "17745550001",
  "from": "18885551234",
  "timestamp": "2026-04-24T18:30:00Z",
  "tracking-id": "abc123xyz",
  "client-reference": "send-001"
}

Example: N102 delivered

{
  "origin": "MMS_MT",
  "code": "N102",
  "sent-as": "MMS",
  "status": "Delivered",
  "status-details": "Message Delivered",
  "to": "17745550001",
  "from": "18885551234",
  "timestamp": "2026-04-24T18:31:10Z",
  "tracking-id": "abc123xyz",
  "client-reference": "send-001",
  "handset": "Apple iPhone"
}

Example: E102 rejected

{
  "origin": "MMS_MT",
  "code": "E102",
  "sent-as": "MMS",
  "status": "Rejected",
  "status-details": "Message Rejected",
  "to": "17745550001",
  "from": "18885551234",
  "timestamp": "2026-04-24T18:32:00Z",
  "tracking-id": "abc123xyz",
  "client-reference": "send-001",
  "error-info": "Delivery was not successful."
}

Example: N003 saved MMS ready

{
  "origin": "MMS_MT",
  "code": "N003",
  "status": "Transcoding successful",
  "status-details": "MMS template is available for sending.",
  "mms-id": "123456",
  "tracking-id": "template-build-001",
  "client-reference": "template-build-001",
  "timestamp": "2026-04-24T18:33:00Z"
}