1.3.0-beta

• Initial Stitch support

1.2.1

• Add getCost() support to Number objects - thanks @arubacao!

1.2.0

• Add support for auto-topup
• Add support for submitting SMS/Voice conversions to Nexmo

1.1.3

• Fix User-Agent header to use Title-Case
• Update VERSION constant in Client.php

1.1.2

• Add ability to specify additional parameters when searching numbers that you own

v1.1.1

• Fix issue with PUT /call where the endpoint may return a 204 response with no body payload

v1.1.0

Added the following functionality:

• Support for downloading call recordings
• Search available numbers
• Purchase number
• Cancel number
• Search SMS rejections
• Number insights standard/advanced support

v1.0.0

Merge master->develop for 1.0.0 release

Beta 4 - More Call API Support

🔨 Changed how underlying collection / resource concepts are applied:

• Moving to both collections and resources being client aware.
• Moving away from the concept of each API having a 'client' (now represented by collections / resources)

✨ Added live call support:

$call->stream->setUrl($url);
$call->stream->put();
Need to add fluent interface, and some convience methods.

✨ Can pass arbitrary data to JWT generation:

Per general spec (#22)

🔨 Update of signature generation:

Based on changes to the API: #29

Beta 3 - New APIs!

Adds support for:
Applications:

• Create an application using an array, or an application entity.
• Iterate over applications (with automatic paging).
• Update and delete applications using string UUIDs and arrays, or the richer entity support.

Numbers:

• Get and update an owned number.
• No support for listing owned numbers, or buying numbers in this release.
• Does support associating a number with an application.

Calls:

• Supports creating calls with the new voice API. Can use rich entities or array structures.
• Get individual calls using their UUID.
• No support for iterating over the calls collection, or manipulating live calls in this release.

JWTs:

• Adds a new Keypair credential, used to generate JWTs.
• Allows multiple credentials to be used at the same time, client understands that JWTs must be used for the new Voice API.