Stay organized with collections
Save and categorize content based on your preferences.
This document clarifies how the RBM platform handles message sending and other
API interactions, distinguishing between synchronous and asynchronous
operations.
RBM API interactions generally follow a synchronous request-response pattern at
the HTTP level. However, the results of many API calls, especially message
delivery, are handled asynchronously through webhooks. Refer to the following
sections for details.
The phones.agentMessages.create
API request is processed synchronously from the API
perspective. When you make an HTTP request to the RBM platform, the server
responds almost immediately with a standard HTTP status code
(like 200 OK or an error) to indicate whether the request was
received and is valid.
However, the actual delivery of the message to the end user is
processed asynchronously. The following factors can affect this process:
Recipient status: The user might be offline, have an empty battery, or not
have RCS enabled.
Network conditions: Carrier network issues can delay or prevent message
delivery.
The RBM platform provides message delivery status updates (like delivery
receipts and read receipts) asynchronously through
webhooks.
Therefore, while the initial API request is synchronous, you should rely on
asynchronous webhook events
to track message delivery. Don't expect immediate confirmation of delivery
status from the
phones.agentMessages.create
response.
Other RBM API interactions
Most other HTTP-based RBM APIs also operate with a synchronous request-response
model. These APIs provide an immediate HTTP response that indicates the status
of the request (success or error). However, while the request is synchronous,
the actions resulting from the request might involve asynchronous processes.
For example, a successful response to an API call to update agent information
doesn't mean the update is instantly reflected everywhere; there might be a
short propagation delay.
Webhook endpoint: Asynchronous events
The following events
are delivered asynchronously to your webhook
endpoint:
Incoming user messages: The RBM platform pushes incoming user messages to
your webhook endpoint. Be sure to verify incoming messages.
Delivery and read receipts: Notifications of message delivery and read
status are sent through webhooks.
Conversation events: Some conversation-related events, such as typing
indicators, are sent through webhooks.
Message expiration and revocation events: The RBM platform sends events to
confirm whether an expired message was successfully revoked.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-02-10 UTC."],[[["\u003cp\u003eRBM API interactions use a synchronous request-response model at the HTTP level, providing immediate feedback on request validity.\u003c/p\u003e\n"],["\u003cp\u003eMessage delivery in the RBM platform is processed asynchronously, relying on webhooks for updates due to factors like recipient status and network conditions.\u003c/p\u003e\n"],["\u003cp\u003eWhile the initial API request for sending messages is synchronous, delivery and read receipts are provided asynchronously through webhook events.\u003c/p\u003e\n"],["\u003cp\u003eOther RBM API interactions follow a synchronous pattern for request handling, but resulting actions may involve asynchronous processes with potential delays.\u003c/p\u003e\n"],["\u003cp\u003eThe RBM platform delivers various asynchronous events, such as incoming user messages, delivery receipts, and conversation updates, through a designated webhook endpoint.\u003c/p\u003e\n"]]],[],null,["# Synchronous and asynchronous operations in RBM\n\nThis document clarifies how the RBM platform handles message sending and other\nAPI interactions, distinguishing between synchronous and asynchronous\noperations.\n\nRBM API interactions generally follow a synchronous request-response pattern at\nthe HTTP level. However, the results of many API calls, especially message\ndelivery, are handled asynchronously through webhooks. Refer to the following\nsections for details.\n\nMessage sending: Synchronous request, asynchronous delivery\n-----------------------------------------------------------\n\nThe [`phones.agentMessages.create`](/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create)\nAPI request is processed **synchronously** from the API\nperspective. When you make an HTTP request to the RBM platform, the server\nresponds almost immediately with a standard HTTP status code\n(like `200 OK` or an error) to indicate whether the request was\nreceived and is valid.\n\nHowever, the actual delivery of the message to the end user is\nprocessed **asynchronously**. The following factors can affect this process:\n\n- **Recipient status**: The user might be offline, have an empty battery, or not have RCS enabled.\n- **Network conditions**: Carrier network issues can delay or prevent message delivery.\n\nThe RBM platform provides message delivery status updates (like delivery\nreceipts and read receipts) asynchronously through\n[webhooks](/business-communications/rcs-business-messaging/guides/integrate/webhooks).\nTherefore, while the initial API request is synchronous, you should rely on\nasynchronous webhook [events](/business-communications/rcs-business-messaging/guides/build/events#agent-generated_events)\nto track message delivery. Don't expect immediate confirmation of delivery\nstatus from the\n[`phones.agentMessages.create`](/business-communications/rcs-business-messaging/reference/rest/v1/phones.agentMessages/create)\nresponse.\n\n### Other RBM API interactions\n\nMost other HTTP-based RBM APIs also operate with a synchronous request-response\nmodel. These APIs provide an immediate HTTP response that indicates the status\nof the request (success or error). However, while the request is synchronous,\nthe actions resulting from the request might involve asynchronous processes.\nFor example, a successful response to an API call to update agent information\ndoesn't mean the update is instantly reflected everywhere; there might be a\nshort propagation delay.\n\nWebhook endpoint: Asynchronous events\n-------------------------------------\n\nThe following [events](/business-communications/rcs-business-messaging/guides/build/events#agent-generated_events)\nare delivered asynchronously to your [webhook](/business-communications/rcs-business-messaging/guides/integrate/webhooks)\nendpoint:\n\n- **Incoming user messages** : The RBM platform pushes incoming user messages to your webhook endpoint. Be sure to [verify incoming messages](/business-communications/rcs-business-messaging/guides/integrate/webhooks#verify_incoming_messages).\n- **Delivery and read receipts**: Notifications of message delivery and read status are sent through webhooks.\n- **Conversation events**: Some conversation-related events, such as typing indicators, are sent through webhooks.\n- **Message expiration and revocation events**: The RBM platform sends events to confirm whether an expired message was successfully revoked."]]