SMS - OVHcloud SMS API: Are PTT Codes Always Reporting 0 for delivered and Undelivered SMS?
... / OVHcloud SMS API: Are PTT...
BMPCreated with Sketch.BMPZIPCreated with Sketch.ZIPXLSCreated with Sketch.XLSTXTCreated with Sketch.TXTPPTCreated with Sketch.PPTPNGCreated with Sketch.PNGPDFCreated with Sketch.PDFJPGCreated with Sketch.JPGGIFCreated with Sketch.GIFDOCCreated with Sketch.DOC Error Created with Sketch.
Frage

OVHcloud SMS API: Are PTT Codes Always Reporting 0 for delivered and Undelivered SMS?

Von
mz2025
Erstellungsdatum 2025-06-27 18:03:48 in SMS

Hi everyone,

I'm hitting a roadblock with the OVHcloud SMS API's delivery status reporting, and I'm hoping you can shed some light on it.

When I use GET /sms/{serviceName}/outgoing/{id} to check SMS status, the ptt code always returns 0. This is happening both when message is successfully received and even when messages clearly aren't delivered – for instance, to unallocated or out-of-service numbers.

The strange part? The OVH dashboard does show these messages status (delivered or failed), so the delivery information exists within the system. My understanding from GET /sms/ptts is that codes like 1 (retrying), 8 (expired), or 24 (subscriber absent/phone off) should be reported in the failure cases, but I'm only ever seeing ptt: 0.

Has anyone else experienced the ptt code inaccurately reflecting non-delivery or message expiration? Am I misinterpreting something, or is this a known issue?

Any insights, workarounds, or confirmation that you've seen this behavior would be incredibly helpful!

Thanks,