capabilities.work

Send an A2P SMS Batch and Reconcile Statuses

A 3-step recipe with RingCentral. We can help you get access.

Recipe · 3 steps

Send an A2P SMS Batch and Reconcile Statuses

Submit an A2P SMS batch, wait for it to finish processing, and aggregate delivery statuses.

  1. Submit the A2P SMS batch. RingCentral validates the sender registration, accepts the batch, and returns the batch id, the accepted batch size, and the list of rejected/invalid recipients.
  2. Read the batch back until RingCentral reports it as "Completed". While the batch is still "Processing" the delivery counts are not yet final, so this step repeats before the statuses are aggregated.
  3. Aggregate the delivery status counts for the batch. This is the reporting call an integrator runs to track how much of a campaign was delivered versus queued or failed.
What you'll need to have ready
  • accountId: Internal identifier of the RingCentral account. Use "~" for the account associated with the current authorization session.
  • fromPhoneNumber: The registered A2P sender phone number in E.164 format (e.g. +15551234567).
  • text: Default message text applied to every message in the batch. Individual messages may override it.
  • recipients: Recipient phone numbers in E.164 format. Each becomes one message in the batch.
  • dateFrom: Start of the reporting window used when aggregating batch statuses (ISO 8601).
For your developer

Arazzo workflow ringcentral:send-a2p-batch-reconcile, 3 operations: createA2PSMS → readA2PBatch → aggregateA2PSMSStatuses. Specs on APIs.io.