We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Using Messages API to send messages with fail-over is not possible due to incomplete model classes.
Version: infobip-api-java-client:4.3.2
infobip-api-java-client
4.3.2
Some classes lack required attributes, which interferes with using Messages API corectly.
com.infobip.model.MessagesApiFailover
content
com.infobip.model.MessagesApiTemplateMessage
failover
com.infobip.model.MessagesApiTemplateMessage.destinations
destinations
...MessagesApiToDestination
...MessagesApiTemplateMessage
...MessagesApiMessageDestination
The expected behaviour is a successful delivery of a :
This issue is just about the inconsistent API model classes, and does not necessarily claim that the actual service will work as intended.
The text was updated successfully, but these errors were encountered:
The issue seems to have been resolved in #46 and the related version 4.4.0
Sorry, something went wrong.
No branches or pull requests
Using Messages API to send messages with fail-over is not possible due to incomplete model classes.
Version:
infobip-api-java-client
:4.3.2
Some classes lack required attributes, which interferes with using Messages API corectly.
com.infobip.model.MessagesApiFailover
content
attributecom.infobip.model.MessagesApiTemplateMessage
failover
attributecom.infobip.model.MessagesApiTemplateMessage
.destinations
...MessagesApiToDestination
...MessagesApiTemplateMessage
...MessagesApiMessageDestination
insteadThe expected behaviour is a successful delivery of a :
This issue is just about the inconsistent API model classes, and does not necessarily claim that the actual service will work as intended.
The text was updated successfully, but these errors were encountered: