Infobip Client does not work with Infobip

[minglecm]

After upgrading to the latest Infobip client we're seeing errors returned from Infobip that seem to be caused by this commit: 3e36f8e

While that commit brings oneapi-python up to OneApi standards, it seems to be breaking it's support of Infobip's smsmessaging/outbound endpoint:

https://oneapi.infobip.com/1/smsmessaging/outbound/xxxx/requests

Error:

{"clientCorrelator":null,"serviceException":{"messageId":"MISSING_PARAMETER","text":"Missing parameter","variables":["binary or message"],"additionalDescription":null},"variables":null}}

It seems this endpoint expects message to be at the top level and not nested under outboundSMSTextMessage.

[jiceher]

The message element should be nested in a outboundSMSTextMessage as specified by GSMA. See http://www.gsma.com/oneapi/sms-restful-netapi/ for examples.

[minglecm]

While that is true for the OneApi standard, it does not appear that Infobip supports message nested inside of outboundSMSTextMessage.

Their docs state that message should be top level and includes nothing about outboundSMSTextMessage.

message (string, optional): The text message content.,

We had no problems with the oneapi-python client until upgrading to a version that contained 3e36f8e.

Once reverting as well as cURLing the endpoint manually with message nested and message not nested, it was clear that MISSING_PARAMETER was returned when nested.

[mmilakovic]

@dentafrice You were right. messageshouldn't be nested inside of outboundSMSTextMessage object. This problem was occurring when json was used as data format. After latest commit everything should be working like before mentioned pull request.

We deeply apologize because you had to wait for answer. If you have any other question please contact our support (support@infobip.com) or post your question on github repository.

Best regards,

Milos