4.1.3

This release adds BYOP (Bring Your Own PIN) to Verify V2 (i.e. you can give an alphanumeric string of your choice to be sent to the customer. It also adds a bugfix by @ash-jc-allen who spotted the ClientFactory for the mapper was incorrectly coded like the test suite using Prophecy.

What's Changed

• Feature/verify v2 byop by @SecondeJK in #400
• Fix Verify2 bug that prevents verifications from being sent by @ash-jc-allen in #397

Full Changelog: 4.1.2...4.1.3

4.1.2

The Auth handler rollout broke Verify v1, which needs the api_key and api_secret to be passed into the body. This meant changing the auth to TokenBodyHandler() which has not been used before, and subsequently needed to be fixed.

Verify v1 should now be working correct with auth, and tests have been added to stop repeats of this.

What's Changed

• Fix TokenBodyHandler and add it to Verify v1 by @SecondeJK in #394

Full Changelog: 4.1.1...4.1.2

4.1.1

Routine patch to add getRecording() method to the Voice client.

What's Changed

• Add ability for Voice to get Recording by @SecondeJK in #393

Full Changelog: 4.1.0...4.1.1

4.1.0

This release adds the capability to use Vonage's Verify V2 in the SDK.

What's Changed

• Verify v2 by @SecondeJK in #389
• Verify v2 webhook modifications by @SecondeJK in #392

Full Changelog: 4.0.11...4.1.0

4.0.11

This routine patch release is to primarily remove unsupported Message types in the Message API (as these are no longer available on the Vonage API, they are technically not a backwards-compatible breaking change). There are also some new types of Message supported, notably ViberVideo.

What's Changed

• Remove unsupported message types by @SecondeJK in #385
• New Message Types by @SecondeJK in #388
• Add type to possibleParameters for Number context by @stronglab in #390

New Contributors

• @stronglab made their first contribution in #390

Full Changelog: 4.0.10...4.0.11

4.0.10

This PR has an important behaviour change for sending SMS:
You will now not longer receive a PHP warning if you try and send a GSM-7 charset as Unicode.
You -will- get a logged warning (if you have set a PSR-3 compatible logger when creating the client) if you try and send a unicode charset text that could be set to GSM-7.

We do not want to stop you sending a message - it's your choice what encoding you want to use, but we will warn you if not correct.

GSM-7 is still the default, since unicode creates longer SMS messages that cost more.

What's Changed

• Fix auth handler for Numbers - autoclosed by @SecondeJK in #383
• Change warning to logger for GSM-7 by @SecondeJK in #382

Full Changelog: 4.0.9...4.0.10

4.0.9

This patch fixes the Basic Auth query handler which was overwriting existing query parameters when adding Auth.
It also contains a one line fix for a bug left in #379.

What's Changed

• Forgot to add return value to request by @SecondeJK in #380

Full Changelog: 4.0.8...4.0.9

4.0.8

This is a periodic patch to ship some improvements: the most important being a fix for Clients that use the IterableAPI Collection. This is an internal change. The other important aspect to note with this release is the introduction of deprecation notices for the PayNCCO. This feature will be deleted in a future major release, as it is being removed from Vonage APIs.

What's Changed

• Deprecate Pay NCCO by @SecondeJK in #377
• Fix Voice Webhook Typo by @SecondeJK in #378
• Fix IterableAPICollection Auth Handling by @SecondeJK in #379

Full Changelog: 4.0.7...4.0.8

4.0.7

This release fixes the authorisation handling for the Account API by introducing the new BasicQueryHandler()

What's Changed

• added missing query string auth, add to account api by @SecondeJK in #372

Full Changelog: 4.0.6...4.0.7

4.0.6

This release is a hotfix for the GSM-7 detection, which contained an incorrect regex.

What's Changed

• Bug/missing square bracket escape gsm7 by @SecondeJK in #367

Full Changelog: 4.0.5...4.0.6