When to Use Asynchronous Processing

Asynchronous processing is not necessary for all your API calls. Analyze these scenarios to identify which API calls are best suited for asynchronous processing.

Async ScenarioDescription
High AvailabilityIf Marketing Cloud is unavailable or undergoing maintenance, your API calls are accepted and queued.
Instant ResponseThe asynchronous server responds instantly to let your system know that the call has been queued, even if the call is scheduled for future processing.
Sequential ProcessingTo process multiple API calls in sequence, use the conversation concept. Multiple calls sent synchronously could process out of order, but the sequence numbers you assign to the calls in the conversation ensure the correct processing order.
Avoid DuplicationOften, it is important not to repeat an API call, even if the call is sent more than once. For example, you don't want to send the same email message multiple times. The conversation concept prevents duplicate processing of API calls because each ConversationID must be unique and cannot be processed more than once.
Scheduled API CallsTo schedule a date and time to process the call, use the Options parameter.
Multiple Notification MechanismsChoose whether to receive notifications regarding your API calls via email, HTTP POST, or Retrieve.
Prioritize SendsChoose the order and frequency in which items in the asynchronous queue are processed.