Release 6.2.0

[ib-tjuhasz]

[ 6.2.0 ] - 2025-10-27

⚠️ 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.
  • Infobip Voice API.
  • Infobip SMS API.
  • Infobip 2FA API.
  • Infobip Email API.
  • Infobip WhatsApp API.
  • Infobip Viber API.
  • Infobip WebRTC API.
  • Infobip Moments.
  • Infobip MMS API.

Changed

• Email:

  • For getIpPool method response type changed from EmailIpPoolResponse to EmailIpPoolDetailResponse
  • Removed returnPathAddress field from EmailAddDomainRequest, EmailDomainResponse model
  • /email/1/domains/{domainName}/return-path - This endpoint has been is no longer supported in the SDK.
  • Fixed bulks field in EmailBulkScheduleResponse and EmailBulkStatusResponse, now initialized as an empty list due to field change from optional to required
  • Extended EmailDomainResponse model with blocklistConfigrationLevel field
  • Extended EmailIpDetailResponse, EmailIpResponse model with ipAddresses field
  • Fixed messages field in EmailSendResponse, now initialized as an empty list due to field change from optional to required
  • Fixed reason field type in EmailValidationResponse from String to EmailValidationReason
  • Fixed risk field type in EmailValidationResponse from String to EmailValidationApiRisk
  • Extended EmailWebhookTrackingPayload model with eventId and sender field support
  • JavaDoc fixes

• MessagesApi:

  • Extended MessagesApiDefaultMessageRequestOptions with messageOrdering field support
  • Extended MessagesApiMessageBody with FORM, ORDER_REQUEST, ORDER_STATUS and TIME_PICKER body type support
  • Extended MessagesApiMessageButton with DIAL_PHONE and SHOW_LOCATION button type support
  • Extended MessagesApiMessageOpenUrlButton model with postbackData and openIn field support
  • Extended MessagesApiMessageOptions model with transliteration and correlationData field support
  • Extended MessagesApiOutboundTemplateChannel model with VIBER_BM type support
  • Extended MessagesApiWebhookEventContent model with FORM_RESPONSE and PAYMENT_RESPONSE event type support
  • Extended MessagesApiWebhookEvent with messageCount and metadata field support
  • JavaDoc fixes

• Mms:

  • Cursor-based pagination support in getOutboundMmsMessageLogs function with useCursor and cursor parameters.
    • Extended MmsLogsResponse model with cursor field
  • JavaDoc fixes

• Moments:

  • Fixed FlowExceptionResponse model with adding missing fields: type, title, status, detail, instance
  • JavaDoc fixes

• Sms:

  • Unified SmsWebhookInboundReport with the existing SmsInboundMessage model
  • Unified SmsWebhookInboundReportResponse with the existing SmsInboundMessageResult model
  • JavaDoc fixes

• Tfa:

  • Extended TfaCreateEmailMessageRequest, TfaMessage, TfaUpdateEmailMessageRequest and TfaEmailMessage with landingPageId field support
  • Extended TfaStartEmailAuthenticationRequest with landingPagePlaceholders field support
  • JavaDoc fixes

• Viber:

  • Cursor-based pagination support in getOutboundViberMessageLogs function with useCursor and cursor parameters.
    • Extended ViberLogsResponse model with cursor field
  • Extended ViberMessageDeliveryReporting with receiveTriggeredFailoverReports field support
  • Extended ViberOutboundFileContent and ViberOutboundFileContentType with a CAROUSEL support
  • JavaDoc fixes

• Voice:

  • Class replaced in updateConferenceCall method from CallsUpdateRequest to CallsUpdateCallRequest to better reflect its specific usage
  • Extended Call, CalLog, CallRequest models with new field: externalId
  • Extended CallEndpoint, CallRoutingEndpoint models with WHATSAPP type support
  • Extended CallRoutingDestination model with APPLICATION type support
  • Extended CallRecordingRequest model with new field: channels
  • Extended CallRoutingPhoneEndpoint model with new field: ringbackGeneration
  • Extended CallRoutingRouteResponse model with new fields: status and order
  • Extended CallRoutingSipEndpoint model with new field: from
  • Extended CallsAddExistingCallRequest model with new fields: role and customData
  • Extended CallsAddNewCallRequest with role support
  • Extended CallsMachineDetection model with machineDetection support
  • Extended CallsDialogState with TRANSFERRING state support
  • Removed UNKOWN enum value from CallsDetectionResult enum
  • Removed creationMethod field from CallsFile model
  • Extended CallsLanguage with multiple new language options
  • Extended CallsMachineDetectionProperties with confidenceRating field support
  • Extended CallsMachineDetectionRequest with detectionTime field support
  • Extended CallsParticipant with role field support
  • Extended CallsSearchResponse, CallsUpdateScenarioRequest, CallsUpdateScenarioResponse model with new fields: notifyUrl and notifyContentType
  • Fixed CallsSpeechCaptureRequest keyPhrases now are null instead of being initialized as a new LinkedHashSet to reflect field change from required to optional
  • Extended CallsTranscription model with new fields: customDictionary and advancedFormatting
  • Extended CallsUpdateRequest, CallsVideoMediaProperties model with new blind field support
  • Extended CallsVoiceData with new field support: answeredBy
  • Extended CallsWebsocketEndpointConfigRequest.SampleRateEnum with new rate values: 24000 and 32000
  • Extended CallVoice with new voices
  • JavaDoc fixes

• Number Masking:

  • Extended NumberMaskingStatusRequest with machineDetectionResult field support
  • JavaDoc fixes

• WebRtc:

  • Removed capabilites field from WebRtcTokenRequestModel to reflect the current behaviour of the endpoint
  • Extended WebRtcParticipant with state and direction field support
  • JavaDoc fixes

• WhatsApp:

  • Extended WhatsAppWebhookType with new types: INTERACTIVE_CALL_PERMISSION_REPLY and REACTION
  • Extended WhatsAppVideoMessage, WhatsAppAudioMessage, WhatsAppContactsMessage, WhatsAppDocumentMessage, WhatsAppImageMessage, WhatsAppInteractiveButtonsMessage, WhatsAppInteractiveFlowMessage, WhatsAppInteractiveListMessage, WhatsAppInteractiveLocationRequestMessage, WhatsAppInteractiveMultiProductMessage, WhatsAppInteractiveOrderDetailsMessage, WhatsAppTextMessage, WhatsAppInteractiveOrderStatusMessage, WhatsAppStickerMessage, WhatsAppMessage, WhatsAppLocationMessage, WhatsAppInteractiveProductMessage, WhatsAppInteractiveUrlButtonMessage models with context field support
  • Removed allowCategoryChange field from WhatsAppTemplatePublicApiRequest model to reflect the current behaviour of the endpoint
  • Extended WhatsAppTemplateEditPublicApiRequest, WhatsAppDefaultUtilityTemplateApiResponse models with subCategory field support
  • Extended WhatsAppTemplateDataContent model with orderStatus field support
  • Extended WhatsAppSenderLimit model with additional value (LIMIT_2K)
  • Fixed callbackData field type in WhatsAppPayment model from List<String> to Object reflecting the current behaviour of the endpoint
  • Extended WhatsAppLanguage with multiple new language options
  • Extended WhatsAppInteractiveUrlButtonHeaderContent with DOCUMENT, IMAGEandVIDEO` type support
  • Extended WhatsAppInteractiveOrderUPIPGRazorpayPaymentDetails with callbackData field support
  • Extended WhatsAppInteractiveOrderPaymentStatus with BRAZIL_BOLETO status support
  • Extended WhatsAppInteractiveAllowedOrderPaymentDetails with BRAZIL_BOLETO and BRAZIL_PAYMENTS type support
  • Extended WhatsAppDefaultTemplateStructureApiData with callPermissionRequest field support
  • Extended WhatsAppButtonApiData with ORDER_DETAILS and VOICE_CALL type support
  • JavaDoc fixes

• General:

  • Updated tests

Removed

• Unused EmailReturnPathAddressRequest, CallsCreationMethod, WebRtcCapabilities, WebhookMessageCount and WebRtcRecording classes are removed

[github-advanced-security]

This pull request sets up GitHub code scanning for this repository. Once the scans have completed and the checks have passed, the analysis results for this pull request branch will appear on this overview. Once you merge this pull request, the 'Security' tab will show more code scanning analysis results (for example, for the default branch). Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results. For more information about GitHub code scanning, check out the documentation.

[ib-tjuhasz]

We'll address Sonar analysis in later phases. The most of the reported issues are related to the fact that the majority of the code is fully auto-generated from the OpenAPI specification which results in duplicated segments. We'll tweak the policies and make sure to handle all the possible readability issues. In addition to that, the PR brings a fresh set of tests. However, we don't measure coverage directly, but we'll include it as well in later phases.