Hi Alexander, Are you 100% sure the "Batch ID" returned from sending SMS in a batch is the same as "Message ID"? As I understand, in one (1) "batch", it's possible to send to multiple recipients. That means multiple message in a single batch, each with their own unique message ID. For instance, suppose I send one "batch" message with two recipients (Jane and John) by using POSTing to the "/batches" endpoint as described here: https://developers.sinch.com/docs/sms/api-reference/sms/tag/Batches/#tag/Batches/operation/SendSMS That POST will return 1 "Batch ID", but result in 2 SMS message (to Jane and John). In "Message search", there will be 2 separate entries to John's and Jane's phone numbers, with different Message IDs. Correct? When I send a batch, the format of the Batch ID looks like this: "03E5R4D7P2D2GW1JVTC6TBE3DB". When I look in Message search, the format of the Message ID looks like this: "1326a43de7000001d82e534b22356eba" To me it seems Batch ID and Message ID have different formats. What I'd be looking for here is to not only get the "Batch ID", but also an array of the "Message IDs" as return value to the request. I've seen it's possible to request "delivery report callback", but that doesn't provide the message ID either. Also, with a callback, it's difficult to correlate the delivery report with the batch command, since the callback is asynchronous and comes later. It's also not desirable that an application developer needs to host an API on the Internet just to get responses. If you compare with competition, for instance Twilio returns a message ID that you can search for in their "message search". Can you please check with your developers how Message IDs can be returned as response to a batch request? Also, how to get the Message ID as HTTP response to the original request (as opposed to having to host an API to get an asynchronous callback). Thanks in advance.
... View more
