Skip to content

6.2.0
Compare
Choose a tag to compare
@ib-fsrnec ib-fsrnec released this 20 Jan 21:21
· 1 commit to master since this release
6.2.0
90f5142
This commit was created on github.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

[ 6.2.0 ] - 2025-01-20

⚠️ IMPORTANT NOTE: This release contains breaking changes!

Added

  • Support for Calls Configuration.
  • Additional validation for WhatsApp sender parameters.
  • Support for Email IP Management instead of set of deprecated Email IP endpoints.
    Check Email API documentation for additional details (BREAKING).
  • 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.
  • Support for OTP templates for Viber messages. For additional details check Viber API documentation.
  • Support for telemarketerId in India DLT options when sending failover SMS messages through Viber API.
  • Support for cache duration when playing audio files by providing the URL to the audio file in Calls API.
  • New Call state: DISCONNECTED.
  • Support for downloading Voice IVR recorded files. Check the Voice API documentation for additional details.

Changed

  • Email Suppression type enum models are now consolidated. Use EmailSuppressionType and EmailAddSuppressionType instead of EmailAddDeleteSuppressionType and Infobip/Model/EmailGetSuppressionType (BREAKING).
  • Don't allow empty text when sending failover SMS messages through Viber API.
  • Explicitly allow enum denormalization only for string types.
  • Extend OneOfInterfaceNormalizer with enum support.
  • Adjusted Call Voice models, so both CallsVoice and CallsSynthesisVoice are used in the correct context (BREAKING).
  • Adjusted Call Language models, so both CallsLanguage and CallTranscriptionLanguages are used in the correct context (BREAKING).

Fixed

  • Issue #67: Fetching WhatsApp media metadata methods now return an array that contains header values provided by the API.
    Check the API Documentation and the ReceiveWhatsAppApiTest for additional details.
  • EmailSuppressionInfo model to correctly specify DateTime type for createdDate field.
  • Invalid type hints for map-like properties.
  • Number Masking:
    • DELETE requests and error processing
    • Content schema when uploading audio files
    • UTC date-time deserialization in setup response model.
  • Interactive Voice Response:
    • lastUsageDate filed processing (yyyy-MM-dd format)
    • Adjusted models in script processing
Assets 2
Loading