RCS API Logo

Status codes

Create development account

Below is a summary of the status codes, which are divided into four groups. The group a code belongs to is determined by its first digit; codes starting with 1, for example, belong to the ”Accepted” group.

This allows us to add new status codes while your software can still handle these new status codes without being explicitly developed for them.

Code block #

NameCode blockDescription of the project
Accepted1Informative statuses that inform about where the message is located in the pipeline.
Success2If the message ended in a user-defined way such as Expired or DeliveredToHandset
Rejection4If the message could not be delivered or other errors that are beyond the control of the delivery service.
Error5If the message could not be delivered or other errors that are beyond the control of the delivery service.

Statuses within the Accepted code block #

NameStatus codeCode blockDescription of the project
Accepted101AcceptedThe message/messages have been approved for processing.
Queued102AcceptedThe message has been added to a queue for transmission.
Funded103AcceptedThe message has been paid for and can be sent.
Refunded104AcceptedThe payment for the message has been refunded, meaning that the amount has been returned to the account balance.
DeliveredToGateway111AcceptedThe message has been delivered to the next upstream gateway.
DeliveredToNetwork112AcceptedThe message has been sent but has not yet reached the client.
QuedAtGateway114AcceptedThe message has been queued in the next upstream gateway.
FallbackPending121AcceptedThe message will be sent using a fallback option, but has not yet been sent to the next upstream gateway.
FallbackQueued122AcceptedThe message has been queued for transmission using the backup option.
FallbackDeliveredToGateway123AcceptedThe message has been delivered to the next upstream gateway using the fallback option.

Statuses within the Success code block #

NameStatus codeCode blockDescription of the project
DeliveredToHandset201SuccessThe message has been delivered to the appropriate recipient.
Expired202SuccessThe expiration date has passed before the message could be delivered.
Cancelled203SuccessThe message was interrupted by the user
Read204SuccessThe message was read by the recipient.

Statuses within the Rejection code block #

NameStatus codeCode blockDescription of the project
InsufficientFunds402RejectionThe account does not have enough funds to send the message.
RecipientRejected405RejectionThe recipient is invalid or blocked.
GenericRejected406RejectionThe notification was rejected for a reason other than the above alternatives.
InvalidContent408RejectionThe content of the message is invalid. For example, disallowed characters, too long etc.
InvalidRecipient409RejectionThe recipient of the message is invalid. The recipient is, for example, not a valid MSISDN.
MissingRcsCapability410RejectionThe recipient does not support RCS or cannot receive RCS for other reasons.
AgentInactive420RejectionThe sending agent is not active.
FallbackRejected421RejectionIndicates that the fallback call was rejected; see the fallback message for details.

Status codes in the Error code block #

NameStatus codeCode blockDescription of the project
InternalError500ErrorAn unknown error occurred.
Subscriber Unreachable502ErrorThe network subscriber was not online and therefore could not receive the message.
DeliveryToGatewayFailed511ErrorThe message could not be delivered to the next upstream gateway.
DeliveryToCarrierFailed512ErrorThe message could not be delivered to the carrier.
FallbackFailed521ErrorIt was not possible to deliver the messages to the recipient's phone using the backup option; see the backup message for more information.
Unknown599ErrorThe message has been forwarded, but no delivery confirmation has been received, or a delivery confirmation has been received that could not be interpreted.
Contents