6.1.0 release (#56)

* java 6.1.0 release

Author: ib-tjuhasz

CHANGELOG.md

@@ -5,6 +5,53 @@ All notable changes to the library will be documented in this file.
 The format of the file is based on [Keep a Changelog](http://keepachangelog.com/)
 and this library adheres to [Semantic Versioning](http://semver.org/) as mentioned in [README.md][readme] file.
 
+## [ [6.1.0](https://github.com/infobip/infobip-api-java-client/releases/tag/6.1.0) ] - 2025-04-09
+
+⚠️ **IMPORTANT NOTE:** This release contains compile time breaking changes.
+All changes, including breaking changes, are addressed and explained in the list bellow.
+If you find out that something was not addressed properly, please submit an issue.
+
+### Added
+* Most recent feature set for:
+  * [Infobip Messages API](https://www.infobip.com/docs/api/platform/messages-api).
+  * [Infobip Voice API](https://www.infobip.com/docs/api/channels/voice).
+  * [Infobip SMS API](https://www.infobip.com/docs/api/channels/sms).
+  * [Infobip 2FA API](https://www.infobip.com/docs/api/platform/2fa).
+  * [Infobip Email API](https://www.infobip.com/docs/api/channels/email).
+  * [Infobip WhatsApp API](https://www.infobip.com/docs/api/channels/whatsapp).
+  * [Infobip Viber API](https://www.infobip.com/docs/api/channels/viber).
+  * [Infobip WebRTC API](https://www.infobip.com/docs/api/channels/webrtc-calls).
+  * [Infobip Moments](https://www.infobip.com/docs/api/customer-engagement/moments).
+  * [Infobip MMS API](https://www.infobip.com/docs/api/channels/mms).
+* **Added** new Viber Outbound Content type: `LIST`.
+* **Added** new MessagesApi message body types: `PRODUCT` and `MIXED`.
+* **Added** new WhatsAppInteractive payment status and payment details type: `UPI_INTENT`.
+* **Added** support for `WEBSOCKET` option in call routing endpoint.
+* **Added** WhatsAppWebhookType support:
+* **Added** support for `INFECTED_CONTENT` and `INTERACTIVE_FLOW_REPLY` types in the `WhatsAppWebhookType` enum.
+
+
+### Changed
+* [WhatsAppWebhookPaymentTransactionNotification](src/main/java/com/infobip/model/WhatsAppWebhookPaymentTransactionNotification.java) model, previously nested enum 'type' and 'status' are now extracted to a separate class.
+* [WhatsAppWebhookPaymentNotification](src/main/java/com/infobip/model/WhatsAppWebhookPaymentNotification.java) model, previously nested enum 'currency' is now extracted to a separate class.
+* **Updated** `WhatsAppTemplateCardContent.buttons` field type from `List<WhatsAppTemplateButtonContent>` → `List<WhatsAppCardAllowedTemplateButtonContent>`.
+* **Updated** `WhatsAppTemplatePublicApiRequest.structure` field type from `WhatAppTemplateStructureApiData` → `Object`.
+* **Updated** `CallsUpdateScenarioResponse.lastUsageDate` field type from `String` → `LocalDate`.
+* **Updated** `CallsSearchResponse.lastUsageDate` field type from `String` → `LocalDate`.
+* **Removed** `EmailWebhookTrackReport` and `EmailWebhookTrackResponse`  in favor of a unified class: `EmailWebhookTrackingPayload`.
+* **Updated** `FormsRequest.formType` field type from `FormType` → `String`.
+* **Removed** `CallSipTrunkLocation` enum class, now processed as a `String`.
+* **Updated** `WhatsAppTemplateEditPublicApiRequest` `category` field: `CategoryEnum` inner enum replaced by the existing `WhatsAppCategory` class enum value.
+* **Updated** `WhatsAppTemplatePublicApiRequest` `category` field: `CategoryEnum` inner enum replaced by the existing `WhatsAppCategory` class enum value.
+* **Replaced** `WhatsAppWebhookAddress` `type` enum with `String` to support more options.
+* **Fixed** `WhatsAppWebhookContact` `birthday` field type: changed from `OffsetDateTime` to `LocalDate`.
+* **Removed** `WhatsAppWebhookPaymentNotification` `CurrencyEnum` inner enum class, replaced by the existing `WhatsAppPaymentStatus` class.
+* **Removed** `WhatsAppTemplateAllowedOrderPaymentDetails` class, replaced by the unified `WhatsAppInteractiveAllowedOrderPaymentDetails` class.
+* Fixed Javadoc.
+
+### Removed
+* **Removed** deviceDetails and networkId fields `MessagesApiDeliveryResult`.
+
 ## [ [6.0.0](https://github.com/infobip/infobip-api-java-client/releases/tag/6.0.0) ] - 2025-02-17
 
 🎉 **NEW Major Version of `infobip-api-java-client`.**
@@ -16,24 +63,24 @@ If you find out that something was not addressed properly, please submit an issu
 
 ### Added
 * Most recent feature set for:
-    * [Infobip Messages API](https://www.infobip.com/docs/api/platform/messages-api).
-        * Footer support for Messages API Message. For additional details check Messages API documentation.
-        * Add calendar event button support for Messages API Message. For additional details check Messages API documentation.
-        * Card options for Carousel and Rich Link body types in Messages API Message. For additional details check Messages API documentation.
-    * [Infobip Voice API](https://www.infobip.com/docs/api/channels/voice).
-        * Support for Calls Configuration.
-    * [Infobip SMS API](https://www.infobip.com/docs/api/channels/sms).
-    * [Infobip 2FA API](https://www.infobip.com/docs/api/platform/2fa).
-    * [Infobip Email API](https://www.infobip.com/docs/api/channels/email).
-        * Support for Email IP Management instead of set of deprecated Email IP endpoints. Check [Email API documentation](https://www.infobip.com/docs/api/channels/email) for additional details.
-    * [Infobip WhatsApp API](https://www.infobip.com/docs/api/channels/whatsapp).
-    * [Infobip Viber API](https://www.infobip.com/docs/api/channels/viber).
-    * [Infobip WebRTC API](https://www.infobip.com/docs/api/channels/webrtc-calls).
-    * [Infobip Moments](https://www.infobip.com/docs/api/customer-engagement/moments).
-    * [Infobip MMS API](https://www.infobip.com/docs/api/channels/mms).
-        * Introduced `/mms/2/messages (V2)`  replacing the `/mms/1/advanced (V1)` endpoint.
-        * Introduced `/mms/2/reports (V2)` replacing `/mms/1/reports (V1)` endpoint.
-        * Introduced `/mms/2/logs (V2)` replacing `/mms/1/logs (V1)` endpoint.
+  * [Infobip Messages API](https://www.infobip.com/docs/api/platform/messages-api).
+    * Footer support for Messages API Message. For additional details check Messages API documentation.
+    * Add calendar event button support for Messages API Message. For additional details check Messages API documentation.
+    * Card options for Carousel and Rich Link body types in Messages API Message. For additional details check Messages API documentation.
+  * [Infobip Voice API](https://www.infobip.com/docs/api/channels/voice).
+    * Support for Calls Configuration.
+  * [Infobip SMS API](https://www.infobip.com/docs/api/channels/sms).
+  * [Infobip 2FA API](https://www.infobip.com/docs/api/platform/2fa).
+  * [Infobip Email API](https://www.infobip.com/docs/api/channels/email).
+    * Support for Email IP Management instead of set of deprecated Email IP endpoints. Check [Email API documentation](https://www.infobip.com/docs/api/channels/email) for additional details.
+  * [Infobip WhatsApp API](https://www.infobip.com/docs/api/channels/whatsapp).
+  * [Infobip Viber API](https://www.infobip.com/docs/api/channels/viber).
+  * [Infobip WebRTC API](https://www.infobip.com/docs/api/channels/webrtc-calls).
+  * [Infobip Moments](https://www.infobip.com/docs/api/customer-engagement/moments).
+  * [Infobip MMS API](https://www.infobip.com/docs/api/channels/mms).
+    * Introduced `/mms/2/messages (V2)`  replacing the `/mms/1/advanced (V1)` endpoint.
+    * Introduced `/mms/2/reports (V2)` replacing `/mms/1/reports (V1)` endpoint.
+    * Introduced `/mms/2/logs (V2)` replacing `/mms/1/logs (V1)` endpoint.
 * **Added** new Calls error code type: `MACHINE_DETECTED`.
 * **Added** support for `CallsProviderSipTrunkUpdateRequest`.
 * **Created** `RawJsonDeserializer` to handle raw JSON deserialization.
@@ -53,9 +100,9 @@ If you find out that something was not addressed properly, please submit an issu
 
 - Voice API
   -  Adjusted IVR models in script processing. Scenario scripting is now implemented as a raw string to increase usability of the feature. Scripts should be passed as strings to the IVR request model in all upcoming SDK versions.
-      - **Updated** `CallsUpdateScenarioRequest.script` field type from `List<CallsScriptInner>` → `String`.
-      - **Updated** `CallsSearchResponse.script` and `else` fields type from `List<Object>` → `String`.
-      - **Updated** `CallsUpdateScenarioResponse.script` field type from `Object` → `String`.
+    - **Updated** `CallsUpdateScenarioRequest.script` field type from `List<CallsScriptInner>` → `String`.
+    - **Updated** `CallsSearchResponse.script` and `else` fields type from `List<Object>` → `String`.
+    - **Updated** `CallsUpdateScenarioResponse.script` field type from `Object` → `String`.
   - **Updated** `CallsGetVoicesResponses.voices` field type from `List<CallsVoice>` → `List<CallsSynthesisVoice>`.
   - **Updated** `CallsSearchResponse.lastUsageDate` field type from `OffsetDateTime` → `String`.
   - **Updated** `CallsSpeechCaptureRequest.language` field type from `CallsLanguage` → `CallTranscriptionLanguage`.
@@ -123,31 +170,31 @@ If you find out that something was not addressed properly, please submit an issu
   - **Removed** `fcmServerKey` field from `WebRtcAndroidPushNotificationConfig`.
 
 ### Removed:
-  - Deprecated functions for sending Viber `Image`, `File`, and `Text` messages have been removed. Use `ViberApi.sendViberMessages` to send messages.
-  - All the Calls IVR script related class and from now on all the scripts are processed as `String`:
-    - `CallsCallApi`
-    - `CallsCapture`
-    - `CallsCollect`
-    - `CallsDial`
-    - `CallsDialToMany`
-    - `CallsDialToWebRTC`
-    - `CallsDialToConversations`
-    - `CallsForEach`
-    - `CallsGoTo`
-    - `CallsHangup`
-    - `CallsIfThenElse`
-    - `CallsMachineDetection`
-    - `CallsPause`
-    - `CallsPlay`
-    - `CallsPlayFromRecording`
-    - `CallsRecord`
-    - `CallsRepeatUntil`
-    - `CallsRepeatWhile`
-    - `CallsSay`
-    - `CallsSendSms`
-    - `CallsSetVariable`
-    - `CallsSwitchCase`
-    - `CallsWhileDo`
+- Deprecated functions for sending Viber `Image`, `File`, and `Text` messages have been removed. Use `ViberApi.sendViberMessages` to send messages.
+- All the Calls IVR script related class and from now on all the scripts are processed as `String`:
+  - `CallsCallApi`
+  - `CallsCapture`
+  - `CallsCollect`
+  - `CallsDial`
+  - `CallsDialToMany`
+  - `CallsDialToWebRTC`
+  - `CallsDialToConversations`
+  - `CallsForEach`
+  - `CallsGoTo`
+  - `CallsHangup`
+  - `CallsIfThenElse`
+  - `CallsMachineDetection`
+  - `CallsPause`
+  - `CallsPlay`
+  - `CallsPlayFromRecording`
+  - `CallsRecord`
+  - `CallsRepeatUntil`
+  - `CallsRepeatWhile`
+  - `CallsSay`
+  - `CallsSendSms`
+  - `CallsSetVariable`
+  - `CallsSwitchCase`
+  - `CallsWhileDo`
 
 These changes align the SDK with the current API specification, ensuring consistency and reliability in future updates.
 

CONTRIBUTING.md

@@ -38,10 +38,10 @@ please follow these guidelines to help us understand your proposal and evaluate
 * **Open a New Enhancement Issue** - if your suggestion is new, please open a new issue and prefix it with "ENHANCEMENT" or "SUGGESTION".
   Please try to title your issue as clearly as possible to summarize your enhancement idea.
 * **Provide a Detailed Description** - in your issue description, try to include as much of the following information:
-    * **Problem:** What problem does this enhancement solve? Why is this feature needed?
-    * **Proposed Solution:** Describe the enhancement or feature you’re suggesting. How should it work? Provide as much detail as possible.
-    * **Alternatives Considered:** Have you thought of other ways to solve the problem? If so, briefly explain why your proposed solution is better.
-    * **Additional Context:** Share any examples, mockups, screenshots, or links to similar implementations (if applicable).
+  * **Problem:** What problem does this enhancement solve? Why is this feature needed?
+  * **Proposed Solution:** Describe the enhancement or feature you’re suggesting. How should it work? Provide as much detail as possible.
+  * **Alternatives Considered:** Have you thought of other ways to solve the problem? If so, briefly explain why your proposed solution is better.
+  * **Additional Context:** Share any examples, mockups, screenshots, or links to similar implementations (if applicable).
 * **Stay Focused and Specific** - try to keep your enhancement idea focused on a single problem or feature. If you have multiple ideas, consider creating separate issues for each to make the discussion easier to follow.
 * **Be Open to Feedback** - we encourage healthy discussion about proposed enhancements. Be open to feedback, as maintainers and other contributors may have questions or alternative suggestions.
 * **Contribute the Enhancement** - if you want implement your suggestion or if you're interested in working on the other people's enhancements yourself, please check the [Pull request](#%EF%B8%8F-pull-request) section on how to do that.

README.md

@@ -27,7 +27,7 @@ The current version of this library includes this subset of Infobip products:
 * [SMS](https://www.infobip.com/docs/api/channels/sms)
 * [MMS](https://www.infobip.com/docs/api/channels/mms)
 * [Voice](https://www.infobip.com/docs/api/channels/voice)
-* [WebRTC](https://www.infobip.com/docs/api/channels/webrtc)
+* [WebRTC](https://www.infobip.com/docs/api/channels/webrtc-calls/webrtc)
 * [Email](https://www.infobip.com/docs/api/channels/email)
 * [WhatsApp](https://www.infobip.com/docs/api/channels/whatsapp)
 * [Viber](https://www.infobip.com/docs/api/channels/viber)
@@ -47,9 +47,9 @@ The library requires Java 11 and is compatible up to and including Java 19.
 Simply add the following in your project's POM file under `dependencies` tag:
 ```xml
 <dependency>
-    <groupId>com.infobip</groupId>
-    <artifactId>infobip-api-java-client</artifactId>
-    <version>6.0.0</version>
+      <groupId>com.infobip</groupId>
+      <artifactId>infobip-api-java-client</artifactId>
+      <version>6.1.0</version>
 </dependency>
 ```
 
@@ -91,7 +91,7 @@ See below, a simple example of sending a single SMS message to a single recipien
         .sender("InfoSMS")
         .addDestinationsItem(new SmsDestination().to("41793026727"))
         .content(new SmsTextContent().text("Hello World from infobip-api-java-client!"));
-    
+
     SmsRequest smsMessageRequest = new SmsRequest()
         .messages(List.of(message));
 ```
@@ -146,22 +146,24 @@ Example of webhook implementation with Spring Web framework:
     @PostMapping("/delivery-reports")
     public void receiveDeliveryReports(HttpServletRequest request) throws IOException {
         SmsDeliveryResult reports = new JSON().deserialize(request.getInputStream(), SmsDeliveryResult.class);
+
         for (SmsDeliveryReport report : reports.getResults()) {
             System.out.println(report.getMessageId() + " - " + report.getStatus().getName());
         }
     }
 ```
-If you prefer to use your own serializer, make note of the supported [date format](https://www.infobip.com/docs/essentials/integration-best-practices#date-formats).
+If you prefer to use your own serializer, make note of the supported [date format](https://www.infobip.com/docs/essentials/api-essentials/integration-best-practices#date-formats).
 You can always take a look at our [implementation](https://github.com/infobip/infobip-api-java-client/blob/master/src/main/java/com/infobip/JSON.java).
 
 #### Fetching delivery reports
 If you are for any reason unable to receive real-time delivery reports on your endpoint, you can use `messageId` or `bulkId` to fetch them.
-Each request will return a batch of delivery reports - only once. See [documentation](https://www.infobip.com/docs/api/channels/sms/sms-messaging/logs-and-status-reports/get-outbound-sms-message-delivery-reports) for more details.
+Each request will return a batch of delivery reports - only once. See [documentation](https://www.infobip.com/docs/api/channels/sms/logs-and-status-reports/get-outbound-sms-message-delivery-reports-v3) for more details.
 
 ```java
     SmsDeliveryResult deliveryResult = smsApi.getOutboundSmsMessageDeliveryReports()
                                              .bulkId("bulkId")
                                              .execute();
+
     for (SmsDeliveryReport report : deliveryResult.getResults()) {
         System.out.println(report.getMessageId() + " - " + report.getStatus().getName());
     }
@@ -173,9 +175,11 @@ Infobip API supports Unicode characters and automatically detects encoding. Unic
 ```java
     SmsPreviewRequest smsPreviewRequest = new SmsPreviewRequest()
             .text("Let's see how many characters will remain unused in this message.");
+
     SmsPreviewResponse previewResponse = smsApi
             .previewSmsMessage(smsPreviewRequest)
             .execute();
+
     System.out.println(previewResponse);
 ```
 

messages-api.md

@@ -8,8 +8,8 @@ The first step is to create an `ApiClient` instance with some configuration.
 
 ````java
     ApiClient apiClient = ApiClient.forApiKey(ApiKey.from(API_KEY))
-        .withBaseUrl(BaseUrl.from(BASE_URL))
-        .build();
+                                   .withBaseUrl(BaseUrl.from(BASE_URL))
+                                   .build();
 ````
 
 With that ready, you can now create an instance of `MessagesApi` which allows you to send messages using Messages API.
@@ -61,7 +61,7 @@ The easiest way to start with Messages API is to send a text message. First you
 Send the message invoking the appropriate send method and store the results in a new variable.
 
 ````java
-    MessagesApiResponse messageInfo = null;
+    MessageResponse messageInfo = null;
     try {
         messageInfo = messagesApi
             .sendMessagesApiMessage(messagesApiRequest)

pom.xml

@@ -4,7 +4,7 @@
 
     <groupId>com.infobip</groupId>
     <artifactId>infobip-api-java-client</artifactId>
-    <version>6.0.0</version>
+    <version>6.1.0</version>
     <packaging>jar</packaging>
 
     <name>infobip-api-java-client</name>

src/main/java/com/infobip/RequestFactory.java

@@ -26,7 +26,7 @@
  */
 final class RequestFactory {
 
-    private static final String USER_AGENT_HEADER_VALUE = "infobip-api-client-java/6.0.0";
+    private static final String USER_AGENT_HEADER_VALUE = "infobip-api-client-java/6.1.0";
 
     private final ApiKey apiKey;
     private final BaseUrl baseUrl;