article [Java SDK] Release 1.6.0 in SDKs

article [Java SDK] Release 1.6.0 in SDKs https://community.sinch.com/t5/SDKs/Java-SDK-Release-1-6-0/ta-p/18156 <DIV class="lia-message-template-content-zone"> <H1>What's Changed</H1> <P> </P> <UL> <LI> <H2>chore</H2> <UL> <LI><STRONG>[feat]</STRONG>: Lazy HTTP client initialization until really required</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Cross domains</H2> <UL> <LI><STRONG>[feat]</STRONG> Relax domains init for Webhooks when credentials are not required</LI> <LI><STRONG>[feat]</STRONG> Validation against missing <CODE>required</CODE> property at protocol level</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Conversation</H2> <UL> <LI><STRONG>[fix]</STRONG> <CODE>CardMessage.media_message</CODE> is now of <CODE>MediaMessage</CODE> type</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ListMessage.media</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>SG</CODE> (Singapore) country defined for WhatsApp order payment details</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ConversationChannelCredentials.credential_ordinal_number</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>LineEnterpriseCredentials</CODE> is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>LineCredentialsField.isDefault</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>SendMessageRequest.message_content_type</CODE> is supported (enum of MessageContentType)</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ChannelSpecificMessage</CODE> classes for WhatsApp: <UL> <LI><CODE>OrderDetails</CODE></LI> <LI><CODE>OrderStatus</CODE></LI> </UL> </LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>CardMessageMedia</CODE> class is deprecated in favor of shared <CODE>MediaMessage</CODE></LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Mailgun <STRONG>as <CODE>PREVIEW</CODE> features</STRONG></H2> <UL> <LI><STRONG>[feat]</STRONG> Support "Emails"</LI> <LI><STRONG>[feat]</STRONG> Support "Templates"</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>SMS</H2> <UL> <LI><STRONG>[fix]</STRONG> Fix contentType VS content_type JSON field name for MediaMessageBodyDetails at protocol level</LI> <LI><STRONG>[fix]</STRONG> body requests defined as required at protocol level</LI> <LI><STRONG>[fix]</STRONG> <CODE>UpdateBinaryRequest.udh</CODE> field is required at protocol level</LI> <LI><STRONG>[feat]</STRONG> <CODE>DryRunPerRecipientDetails.encodingEnum</CODE> defined as an enum</LI> <LI><STRONG>[feat]</STRONG> List batches query parameters is accepting a list <CODE>from</CODE> values of code</LI> <LI><STRONG>[deprecation notice]</STRONG> List batches query parameters accepting a single <CODE>from</CODE> value (replaced by function above)</LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>DryRunPerRecipientDetails.encoding</CODE> is deprecated in favor of <CODE>DryRunPerRecipientDetails.encodingEnum</CODE></LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Voice</H2> <UL> <LI><STRONG>[feat]</STRONG> Define <CODE>AnsweringMachineDetection</CODE> used by <CODE>AnsweredCallEvent</CODE> and <CODE>NotificationEvent</CODE></LI> <LI><STRONG>[feat]</STRONG> <CODE>conferenceId</CODE> field is supported by <UL> <LI><CODE>AnsweredCallEvent</CODE></LI> <LI><CODE>DisconnectCallEvent</CODE></LI> <LI><CODE>IncomingCallEvent</CODE></LI> <LI><CODE>NotificationEvent</CODE></LI> <LI><CODE>PromptInputEvent</CODE></LI> </UL> </LI> <LI><STRONG>[feat]</STRONG> <CODE>NotificationEvent</CODE> support <CODE>destination</CODE> and <CODE>amd</CODE>fields</LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>AnsweredCallEventAnsweringMachineDetection</CODE> is replaced by <CODE>AnsweringMachineDetection</CODE></LI> <LI><STRONG>[deprecation notice]</STRONG> Following backend endpoint deprecation <CODE>applications.queryNumber</CODE> is deprecated</LI> </UL> </LI> </UL> </DIV> Wed, 23 Apr 2025 15:23:20 GMT SinchSDKTeam 2025-04-23T15:23:20Z [Java SDK] Release 1.6.0 https://community.sinch.com/t5/SDKs/Java-SDK-Release-1-6-0/ta-p/18156 <DIV class="lia-message-template-content-zone"> <H1>What's Changed</H1> <P> </P> <UL> <LI> <H2>chore</H2> <UL> <LI><STRONG>[feat]</STRONG>: Lazy HTTP client initialization until really required</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Cross domains</H2> <UL> <LI><STRONG>[feat]</STRONG> Relax domains init for Webhooks when credentials are not required</LI> <LI><STRONG>[feat]</STRONG> Validation against missing <CODE>required</CODE> property at protocol level</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Conversation</H2> <UL> <LI><STRONG>[fix]</STRONG> <CODE>CardMessage.media_message</CODE> is now of <CODE>MediaMessage</CODE> type</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ListMessage.media</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>SG</CODE> (Singapore) country defined for WhatsApp order payment details</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ConversationChannelCredentials.credential_ordinal_number</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>LineEnterpriseCredentials</CODE> is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>LineCredentialsField.isDefault</CODE> field is supported</LI> <LI><STRONG>[feat]</STRONG> New <CODE>SendMessageRequest.message_content_type</CODE> is supported (enum of MessageContentType)</LI> <LI><STRONG>[feat]</STRONG> New <CODE>ChannelSpecificMessage</CODE> classes for WhatsApp: <UL> <LI><CODE>OrderDetails</CODE></LI> <LI><CODE>OrderStatus</CODE></LI> </UL> </LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>CardMessageMedia</CODE> class is deprecated in favor of shared <CODE>MediaMessage</CODE></LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Mailgun <STRONG>as <CODE>PREVIEW</CODE> features</STRONG></H2> <UL> <LI><STRONG>[feat]</STRONG> Support "Emails"</LI> <LI><STRONG>[feat]</STRONG> Support "Templates"</LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>SMS</H2> <UL> <LI><STRONG>[fix]</STRONG> Fix contentType VS content_type JSON field name for MediaMessageBodyDetails at protocol level</LI> <LI><STRONG>[fix]</STRONG> body requests defined as required at protocol level</LI> <LI><STRONG>[fix]</STRONG> <CODE>UpdateBinaryRequest.udh</CODE> field is required at protocol level</LI> <LI><STRONG>[feat]</STRONG> <CODE>DryRunPerRecipientDetails.encodingEnum</CODE> defined as an enum</LI> <LI><STRONG>[feat]</STRONG> List batches query parameters is accepting a list <CODE>from</CODE> values of code</LI> <LI><STRONG>[deprecation notice]</STRONG> List batches query parameters accepting a single <CODE>from</CODE> value (replaced by function above)</LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>DryRunPerRecipientDetails.encoding</CODE> is deprecated in favor of <CODE>DryRunPerRecipientDetails.encodingEnum</CODE></LI> </UL> </LI> </UL> <P> </P> <UL> <LI> <H2>Voice</H2> <UL> <LI><STRONG>[feat]</STRONG> Define <CODE>AnsweringMachineDetection</CODE> used by <CODE>AnsweredCallEvent</CODE> and <CODE>NotificationEvent</CODE></LI> <LI><STRONG>[feat]</STRONG> <CODE>conferenceId</CODE> field is supported by <UL> <LI><CODE>AnsweredCallEvent</CODE></LI> <LI><CODE>DisconnectCallEvent</CODE></LI> <LI><CODE>IncomingCallEvent</CODE></LI> <LI><CODE>NotificationEvent</CODE></LI> <LI><CODE>PromptInputEvent</CODE></LI> </UL> </LI> <LI><STRONG>[feat]</STRONG> <CODE>NotificationEvent</CODE> support <CODE>destination</CODE> and <CODE>amd</CODE>fields</LI> <LI><STRONG>[deprecation notice]</STRONG> <CODE>AnsweredCallEventAnsweringMachineDetection</CODE> is replaced by <CODE>AnsweringMachineDetection</CODE></LI> <LI><STRONG>[deprecation notice]</STRONG> Following backend endpoint deprecation <CODE>applications.queryNumber</CODE> is deprecated</LI> </UL> </LI> </UL> </DIV> Wed, 23 Apr 2025 15:23:20 GMT https://community.sinch.com/t5/SDKs/Java-SDK-Release-1-6-0/ta-p/18156 SinchSDKTeam 2025-04-23T15:23:20Z