Hi guys.
Not sure if this is a bug or not, but when I successfully send an SMS using the /platform_service_sms path, the messageID field in the reponse isn’t the uuid of the newly created SMS.
For instance, the following request:
{
"to": "<mobilenumber>",
"message": "Test message to check API",
"regardingJobUUID": "<uuid>"
}
Returns this response:
{
"errorCode": 0,
"message": "OK",
"messageID": "1fca2d41-7746-4b2c-a88a-24432fd9e82b",
"submittedAt": "2026-06-02T01:46:23+00:00",
"to": "<mobilenmber>"
}
But when listing the SMSs, the record has a different uuid:
{
“uuid”: “85e51507-8395-497d-ba70-2443239557ab”,
“related_object”: “job”,
“related_object_uuid”: “<uuid>”,
“timestamp”: “2026-06-02 11:46:24”,
“direction”: “outbound”,
“sent_by_staff_uuid”: “<uuid>”,
“to_phone”: “<mobilenumber>”,
“from_phone”: null,
“message”: “Test message to check API”
}
If it’s not a bug, is it possible to get the x-record-uuid header field to return the uuid of the created sms, like other Create actions in the API?
Cheers ![]()