Passa al contenuto principale

RCS

Invia messaggi RCS e gestisci template riutilizzabili.

📄️Ottieni lo stato del messaggio RCS

Returns the current delivery status of an RCS (Rich Communication Services) message identified by its messageId. Use this endpoint to track the lifecycle of a specific RCS message after it has been sent. The messageId is the identifier returned in the response when you originally sent the message through the RCS send endpoint. Store this identifier on your side at send time so you can poll for status later. RCS delivery statuses and their meanings: SENT - the message has been accepted by the platform and forwarded to the RCS carrier infrastructure, but delivery to the recipient device has not been confirmed yet. For RCS, this typically means the message is in transit through the Jibe or carrier RCS hub. DELIVERED - the RCS platform confirmed that the message was successfully delivered to the recipient device. This is a reliable delivery receipt provided by the RCS infrastructure, confirming the message arrived on the handset. Note that unlike WhatsApp, standard RCS does not provide a READ status through this API. RECEIVED - the message was acknowledged by the downstream RCS system but final delivery to the handset is not yet confirmed. This is an intermediate state that may appear briefly before transitioning to DELIVERED or ERROR. ERROR - the message could not be delivered. Common causes include: the recipient does not have an RCS-capable device or has RCS disabled, the carrier rejected the message, the agent ID is not properly registered, or the destination number is invalid. Consider implementing an SMS fallback strategy when RCS delivery fails. EXPIRED - the message exceeded its time-to-live window without being delivered and was discarded by the carrier. This can happen when the recipient device is offline for an extended period. UNKNOWN - no status information is available, either because the carrier did not return a delivery receipt or because the message is still being processed. RCS availability depends on carrier support and the recipient having an RCS-capable device with RCS enabled. If you need guaranteed delivery, consider pairing RCS sends with an SMS fallback by checking the status after a reasonable timeout and re-sending via SMS if the status is ERROR or EXPIRED. You can also query RCS message status through the generic delivery status endpoint GET /partner-gateway/v1/messages/status/{customerMessageId}?channel=RCS for a unified cross-channel experience. Error responses: 401 is returned if the API key is missing or invalid. 404 is returned if the messageId does not exist or does not belong to the authenticated company.

Ultimo aggiornamento il