All notable changes to the library will be documented in this file.
The format of the file is based on Keep a Changelog and this library adheres to Semantic Versioning as mentioned in the README.md file.
[ 6.1.0 ] - 2024-12-16
- Support for Infobip Moments.
- Removed no longer supported 50 business-initiated conversations messaging tear limit for WhatsApp senders.
- Added
createdAt
andlastUpdatedAt
fields to WhatsApp Template response models. - Added new Calls error code type:
MACHINE_DETECTED
. CallRoutingWebRtcEndpoint
now allows using defaultto
value used in inbound call as an identity.- Refactored a part of Calls API tests.
- IVR scenario action scripts types.
[ 6.0.0 ] - 2024-12-09
In this release we updated the library to use the latest version of the Infobip API. We also updated the library to use the latest version of the Symfony components. Minimum Symfony version required is 7.0.
🎉 NEW Major Version of infobip-api-php-client
.
- Support for Infobip Messages API.
- Most recent Infobip Voice API feature set.
- Most recent Infobip SMS API feature set.
- Most recent Infobip 2FA API feature set.
- Most recent Infobip MMS API feature set.
- Most recent Infobip Email API feature set.
- Most recent Infobip WhatsApp API feature set.
- Most recent Infobip Viber API feature set.
- Most recent Infobip WebRTC API feature set.
- PHP CS Fixer and PHPStan dev dependencies for code quality checks.
- Additional set of integration tests.
- Require PHP version 8.3 or higher.
- Bumped Symfony components to the latest major version.
- Migration to the new SMS v3 API. Check the README.md for updated examples.
- Introduced the new SmsMessage class to replace
SmsTextualMessage
andSmsBinaryMessage
, providing a unified structure for SMS messaging. - Added a content field within
SmsMessage
to define the message content. This supports both textual and binary messages, which can be created using SmsTextContent or SmsBinaryContent, respectively. - Unified request classes by replacing
SmsAdvancedTextualRequest
andSmsAdvancedBinaryRequest
with the new SmsRequest class. - Consolidated sending functions: use
sendSmsMessages
instead of thesendSmsMessage
andsendBinarySmsMessage
functions.
- Introduced the new SmsMessage class to replace
- Across all Call models, the
applicationId
field has been removed and replaced with theplatform
field, as encapsulates platform fields and reflects the current state of the endpoint. In addition to that, a new requiredcallsConfigurationId
field has been added. - Removed delivery time window configuration classes (
SmsDeliveryTimeWindow
,MmsDeliveryTimeWindow
,ViberDeliveryTimeWindow
,CallRoutingAllowedTimeWindow
,CallsDeliveryTimeWindow
,SmsDeliveryTimeWindow
,CallsTimeWindow
) in favor of a unified class: DeliveryTimeWindow - Removed delivery time configuration classes (
SmsDeliveryTimeFrom
,SmsDeliveryTimeTo
,MmsDeliveryTime
,ViberDeliveryTime
,CallsTimeWindowPoint
,WebRtcTimeOfDay
,CallRoutingAllowedTimeFrom
,CallRoutingAllowedTimeTo
,WebRtcTimeOfDay
) in favor of a unified class: DeliveryTime - Removed URL options configuration classes (
MessagesApiUrlOptions
,ViberUrlOptions
,WhatsAppUrlOptions
) in favor of a unified class: UrlOptions - Removed CPaaS X platform configuration classes (
ViberPlatform
,MessagesApiPlatform
) in favor of a unified class: Platform - Removed delivery day enumeration classes (
SmsDeliveryDay
,MmsDeliveryDay
,CallsDeliveryDay
,CallRoutingAllowedDay
) in favor of a unified class: DeliveryDay - Removed validity period configuration classes (
ViberValidityPeriod
,MessagesApiValidityPeriod
) in favor of a unified class: ValidityPeriod - Removed validity period time unit enumeration classes (
ViberValidityPeriodTimeUnit
,MessagesApiValidityPeriodTimeUnit
) in favor of a unified class: ValidityPeriodTimeUnit - Removed
ModelInterface
since it's no longer needed and not used in serialization anymore.
- Sending Email to multiple recipients.
[ 5.1.4 ] - 2023-06-19
- Update composer.json to match the package version.
[ 5.1.3 ] - 2023-06-19
[ 5.1.2 ] - 2023-06-09
- Removed Snyk
[ 5.1.1 ] - 2023-05-19
- Added composer.lock for Snyk
[ 5.1.0 ] - 2023-04-24
- Obsolete code pre 5.0.0 release (API classes, models)
- Email sending with attachments and inline images
- Updated email README
[ 5.0.0 ] - 2023-03-01
🎉 NEW Major Version of infobip-api-php-client
.
- Support for Infobip MMS API.
- Support for Infobip Voice API.
- Support for Infobip WebRTC API.
- Support for Infobip Viber API.
- Most recent Infobip SMS API feature set.
- Most recent Email feature set.
- Most recent WhatsApp feature set.
- Fully refactored codebase using Symfony components
[ 4.0.0 ] - 2022-10-21
- The minimum supported PHP version has been changed to 8.0
- Get WhatsApp template / Create WhatsApp template have breaking changes as they're using the new v2 API endpoints. The body and footer are no longer strings but objects.
- getEmailLogs' input parameters sentSince and sentUntil now correctly defined as
DateTime
type
- Delete WhatsApp template
[ 3.2.0 ] - 2022-03-29
- Support for Infobip WhatsApp API
- Renamed EmailLogResponse to EmailLogsResponse
- Added default value of false for parameter flash in SmsTextualMessage
- Dev dependencies
- Unused models
[ 3.1.0 ] - 2021-11-19
- Support for Infobip Email API
- Update Guzzle HTTP client version from 6.5 to 7.3
[ 3.0.0 ] - 2021-03-23
🎉 NEW Major Version
In this release, the library is vastly changed and modernized. It is auto-generated and completely different from the previous version, so we do not provide an upgrade guide from 2.x to 3.x because such a document will be a similar size as the library itself.
- Support for async execution
CONTRIBUTING.md
containing guidelines for creating GitHub issues- Support for Infobip Two-factor Authentication API
- Models, structure, examples, etc. for Infobip SMS API
- Library dependencies
README.md
which contains necessary data and examples for quickstart as well as some other important pieces of information on versioning, licensing, etc.- LICENSE which is now MIT
- Support for Infobip Omni API (to be included back in one of the next releases)