In version 1.2.0, we have introduced end-to-end tests for all the supported endpoints. The implementation of these Cucumber steps can be found in the /tests
folder of each API package. These tests run on every push to the repository, providing enhanced protection against potential regressions.
This release also includes several updates to align with the latest API changes and to improve the developer experience. See below for detailed changes in each API package.
Highlights:
[Bugfix] Remove the values set by default by the SDK when formatting the API request.
[Bugfix] In the interface UpdateGroupRequest
, the property name
can also be set to null to remove an existing name set.
[Deprecation Notice] In the interface GetDeliveryReportByPhoneNumberRequestData
, the request parameter recipient_msisdn
is deprecated and should be replaced by phone_number
.
[Deprecation Notice] All variations of a group response (GroupResponse
, CreateGroupResponse
, ReplaceGroupResponse
and UpdateGroupResponse
) are deprecated and replaced by the unique interface Group
.
See full content here: SMS CHANGELOG.md
Highlights:
[Bugfix] Remove the "scheduledProvisioning" properties for SMS and Voice in the update number request.
[Deprecation notice] availableNumber
and activeNumber
subdomain are deprecated and all methods are now defined on the upper numbers service.
All the methods names are the same except availableNumber.list()
-> searchForAvailableNumbers()
Deprecated | New |
---|---|
numbersService.availableNumber.checkAvailability() |
numbersService.checkAvailability() |
numbersService.availableNumber.list() |
numbersService.searchForAvailableNumbers() |
numbersService.availableNumber.rent() |
numbersService.rent() |
numbersService.availableNumber.rentAny() |
numbersService.rentAny() |
numbersService.activeNumber.get() |
numbersService.get() |
numbersService.activeNumber.list() |
numbersService.list() |
numbersService.activeNumber.update() |
numbersService.update() |
numbersService.activeNumber.release() |
numbersService.release() |
See full content here: Numbers CHANGELOG.md
Highlights:
[Bugfix] Fix issue with pagination to iterate over multiple pages.
[Bugfix] conversations.listRecent()
: Add a page_size value by default. Without it the API returns an empty list.
[Bugfix][Breaking] InjectConversationEvent
interface: only AppEvent
is allowed (ContactEvent
and ContactMessageEvent
are no longer allowed).
[Bugfix][Breaking]
See full content here: Conversation CHANGELOG.md
Highlights:
[Breaking] In the interface ConferenceCalloutRequest
, the property mohClass
was declared as a string
and is now a MusicOnHold
type;
[Deprecation Notice] The type VoiceCallback
becomes VoiceCallbackEvent
and is accessible on the Voice
namespace.
See full content here: Voice CHANGELOG.md
Highlights:
[Feature] Support the locale
parameter in the SmsOptions
interface when starting a verification with a SMS.
[Deprecation Notice] All the references to "callout" and "seamless" will be replaced by "phoneCall" and "data" respectively. This change is done to match the code to the online documentation and to enhance the developer experience.
[Deprecation Notice] The type VerificationCallback
becomes VerificationCallbackEvent
and is accessible on the Verification
namespace.
See full content here: Verification CHANGELOG.md
Highlights:
[Feature] Support date rage filter for listing faxes
[Bugfix] Fix faxes.send()
to send one or several faxes over JSON or FormData. Add examples in the simple-examples package.
[Feature][Breaking] Update interfaces according to OAS updates.
See full content here: Fax CHANGELOG.md
Highlights:
[Feature] Add the method accessControlList.get()
.
[Feature] Support date rage filter for listing calls.
[Bugfix][Breaking] callHistory.find()
: the direction
enum's values are in lower case. E.g.: INBOUND
-> inbound
.
[Bugfix][Breaking] The price amount
is now a number
instead of a string
.
See full content here: Elastic SIP Trunking CHANGELOG.md
Meeting Developer needs are important to Sinch. You have an opportunity to provide your honest feedback about your experience onboarding and using our SDK's through a short survey.T
There are fewer than 10 questions and the survey shouldn't take more than a few minutes to complete. All answers are anonymous unless you choose to add your name, email address and company name at the end of the survey.
Our goal is to provide an easy and frictionless experience. Thank you in advance for your time and feedback!
Access the link to complete the survey: Developer Feedback Survey