twilio · Jul 27, 2017 · Jul 27, 2017 · Jul 27, 2017
Showing 424 changed files with 56,641 additions and 88 deletions.
diff --git a/CHANGES.md b/CHANGES.md
@@ -1,6 +1,32 @@
 twilio-node changelog
 =====================
 
+[2017-07-27] Version 4.6.0
+---------------------------
+This release adds Beta and Preview products to main artifact.
+
+Previously, Beta and Preview products were only included in the alpha artifact.
+They are now being included in the main artifact to ease product
+discoverability and the collective operational overhead of maintaining multiple
+artifacts per library.
+
+**Api**
+- Remove unused `encryption_type` property on Recordings *(breaking change)*
+- Update `status` enum for Messages to include 'accepted'
+
+**Messaging**
+- Fix incorrectly typed capabilities property for PhoneNumbers.
+
+**Notify**
+- Add `ToBinding` optional parameter on Notifications resource creation. Accepted values are json strings.
+
+**Preview**
+- Add `sms_application_sid` to HostedNumberOrders.
+
+**Taskrouter**
+- Fully support conference functionality in reservations.
+
+
 [2017-07-13] Version 3.5.0
 ---------------------------
 

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
@@ -0,0 +1,159 @@
+# Contributing to `twilio-node`
+
+We'd love for you to contribute to our source code and to make `twilio-node`
+even better than it is today! Here are the guidelines we'd like you to follow:
+
+ - [Code of Conduct](#coc)
+ - [Question or Problem?](#question)
+ - [Issues and Bugs](#issue)
+ - [Feature Requests](#feature)
+ - [Documentation fixes](#docs)
+ - [Submission Guidelines](#submit)
+ - [Coding Rules](#rules)
+
+## <a name="coc"></a> Code of Conduct
+
+Help us keep `twilio-node` open and inclusive. Please be kind to and considerate
+of other developers, as we all have the same goal: make `twilio-node` as good as
+it can be.
+
+## <a name="question"></a> Got an API/Product Question or Problem?
+
+If you have questions about how to use `twilio-node`, please see our
+[docs][docs-link], and if you don't find the answer there, please contact
+[help@twilio.com](mailto:help@twilio.com) with any issues you have.
+
+## <a name="issue"></a> Found an Issue?
+
+If you find a bug in the source code or a mistake in the documentation, you can
+help us by submitting [an issue][issue-link]. If the file in which the error
+exists has this header:
+```
+"""
+This code was generated by
+\ / _    _  _|   _  _
+ | (_)\/(_)(_|\/| |(/_  v1.0.0
+      /       /
+"""
+```
+then it is a generated file and the change will need to be made by us, but
+submitting an issue will help us track it and keep you up-to-date. If the file
+isn't generated, you can help us out even more by submitting a Pull Request with
+a fix.
+
+**Please see the [Submission Guidelines](#submit) below.**
+
+## <a name="feature"></a> Want a Feature?
+
+You can request a new feature by submitting an issue to our
+[GitHub Repository][github]. If you would like to implement a new feature then
+consider what kind of change it is:
+
+* **Major Changes** that you wish to contribute to the project should be
+  discussed first with `twilio-node` contributors in an issue or pull request so
+  that we can develop a proper solution and better coordinate our efforts,
+  prevent duplication of work, and help you to craft the change so that it is
+  successfully accepted into the project.
+* **Small Changes** can be crafted and submitted to the
+  [GitHub Repository][github] as a Pull Request.
+
+## <a name="docs"></a> Want a Doc Fix?
+
+If you want to help improve the docs in the helper library, it's a good idea to
+let others know what you're working on to minimize duplication of effort. Create
+a new issue (or comment on a related existing one) to let others know what
+you're working on.
+
+For large fixes, please build and test the documentation before submitting the
+PR to be sure you haven't accidentally introduced layout or formatting issues.
+
+If you want to help improve the docs at
+[https://www.twilio.com/docs/libraries/node][docs-link], please contact
+[help@twilio.com](mailto:help@twilio.com).
+
+## <a name="submit"></a> Submission Guidelines
+
+### Submitting an Issue
+Before you submit your issue search the archive, maybe your question was already
+answered.
+
+If your issue appears to be a bug, and hasn't been reported, open a new issue.
+Help us to maximize the effort we can spend fixing issues and adding new
+features by not reporting duplicate issues. Providing the following information
+will increase the chances of your issue being dealt with quickly:
+
+* **Overview of the Issue** - if an error is being thrown a non-minified stack
+  trace helps
+* **Motivation for or Use Case** - explain why this is a bug for you
+* **`twilio-node` Version(s)** - is it a regression?
+* **Operating System (if relevant)** - is this a problem with all systems or
+  only specific ones?
+* **Reproduce the Error** - provide an isolated code snippet or an unambiguous
+  set of steps.
+* **Related Issues** - has a similar issue been reported before?
+* **Suggest a Fix** - if you can't fix the bug yourself, perhaps you can point
+  to what might be causing the problem (line of code or commit)
+
+**If you get help, help others. Good karma rules!**
+
+### Submitting a Pull Request
+Before you submit your pull request consider the following guidelines:
+
+* Search [GitHub][github] for an open or closed Pull Request that relates to
+  your submission. You don't want to duplicate effort.
+* Make your changes in a new git branch:
+
+    ```shell
+    git checkout -b my-fix-branch master
+    ```
+
+* Create your patch, **including appropriate test cases**.
+* Follow our [Coding Rules](#rules).
+* Run the full `twilio-node` test suite (aliased by `make test`), and ensure
+  that all tests pass.
+* Commit your changes using a descriptive commit message.
+
+    ```shell
+    git commit -a
+    ```
+  Note: the optional commit `-a` command line option will automatically "add"
+  and "rm" edited files.
+
+* Build your changes locally to ensure all the tests pass:
+
+    ```shell
+    make test
+    ```
+
+* Push your branch to GitHub:
+
+    ```shell
+    git push origin my-fix-branch
+    ```
+
+In GitHub, send a pull request to `twilio-node:master`.
+If we suggest changes, then:
+
+* Make the required updates.
+* Re-run the `twilio-node` test suite to ensure tests are still passing.
+* Commit your changes to your branch (e.g. `my-fix-branch`).
+* Push the changes to your GitHub repository (this will update your Pull Request).
+
+That's it! Thank you for your contribution!
+
+#### After your pull request is merged
+
+After your pull request is merged, you can safely delete your branch and pull
+the changes from the main (upstream) repository.
+
+## <a name="rules"></a> Coding Rules
+
+To ensure consistency throughout the source code, keep these rules in mind as
+you are working:
+
+* All features or bug fixes **must be tested** by one or more tests.
+* All classes and methods **must be documented**.
+
+[docs-link]: https://www.twilio.com/docs/libraries/node
+[issue-link]: https://github.com/twilio/twilio-node/issues/new
+[github]: https://github.com/twilio/twilio-node
diff --git a/ISSUE_TEMPLATE.md b/ISSUE_TEMPLATE.md
@@ -1,17 +1,18 @@
-*Note: These issues are for bugs and feature requests for the helper libraries. If you need help or support, please email help@twilio.com and one of our experts will assist you!*
+*Note: These issues are for bugs and feature requests for the helper libraries.
+If you need help or support, please email help@twilio.com and one of our experts
+will assist you!*
 
 
 **Version:**
-**API Subdomain (api/taskrouter/ip_messaging):**
 
 ### Code Snippet
-```javascript
-/* paste code here */
+```node
+# paste code here
 ```
 
-### Exception / Log
+### Exception/Log
 ```
-<place exception / log here>
+<place exception/log here>
 ```
 
 ### Steps to Reproduce
@@ -21,5 +22,5 @@
 
 
 ### Feature Request
-_If this is a feature request, make sure you search Issues for an existing request before creating a new one!_
-
+_If this is a feature request, make sure you search Issues for an existing
+request before creating a new one!_
diff --git a/LICENSE.md b/LICENSE.md
@@ -1,8 +1,21 @@
-The MIT License (MIT)
-Copyright (c) 2017 Twilio Inc. help@twilio.com
+MIT License
 
-Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
+Copyright (C) 2017, Twilio, Inc. <help@twilio.com>
 
-The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
+Permission is hereby granted, free of charge, to any person obtaining a copy of
+this software and associated documentation files (the "Software"), to deal in
+the Software without restriction, including without limitation the rights to
+use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies
+of the Software, and to permit persons to whom the Software is furnished to do
+so, subject to the following conditions:
 
-THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.
diff --git a/VERSIONS.md b/VERSIONS.md
@@ -1,65 +1,36 @@
 # Versioning Strategy
 
-`twilio-node` uses a modified version of [Semantic Versioning][semver] for all 
-changes to the helper library.  It is strongly encouraged that you pin at least 
-the major version and potentially the minor version to avoid pulling in breaking 
-changes.
+`twilio-node` uses a modified version of [Semantic Versioning][semver] for
+all changes to the helper library. It is strongly encouraged that you pin at
+least the major version and potentially the minor version to avoid pulling in
+breaking changes.
 
 Semantic Versions take the form of `MAJOR`.`MINOR`.`PATCH`
 
-When bugs are fixed in the library in a backwards compatible way, the `PATCH` 
-level will be incremented by one.  When new features are added to the library 
+When bugs are fixed in the library in a backwards compatible way, the `PATCH`
+level will be incremented by one. When new features are added to the library
 in a backwards compatible way, the `PATCH` level will be incremented by one.
 `PATCH` changes should _not_ break your code and are generally safe for upgrade.
 
-When a new large feature set comes online or a small breaking change is 
-introduced, the `MINOR` version will be incremented by one and the `PATCH` 
+When a new large feature set comes online or a small breaking change is
+introduced, the `MINOR` version will be incremented by one and the `PATCH`
 version reset to zero. `MINOR` changes _may_ require some amount of manual code
-change for upgrade. These backwards-incompatible changes will generally be limited 
-to a small number of function signature changes.
+change for upgrade. These backwards-incompatible changes will generally be
+limited to a small number of function signature changes.
 
-The `MAJOR` version is used to indicate the family of technology represented by 
-the helper library.  It increased from `2.x.x` to `3.x.x` when Twilio moved to 
-auto generation of helper libraries.  Breaking changes that requires extensive 
-reworking of code (like the `2.x.x` to `3.x.x` upgrade) will case the `MAJOR` 
-version to be incremented by one, the `MINOR` and `PATCH` versions will be reset 
-to zero.  Twilio understands that this can be very disruptive, we will only 
-introduce this type of breaking change when absolutely necessary. New `MAJOR` 
-versions will be communicated in advance with `Release Candidates` and a 
-schedule.
+The `MAJOR` version is used to indicate the family of technology represented by
+the helper library. Breaking changes that requires extensive reworking of code
+will case the `MAJOR` version to be incremented by one, and the `MINOR` and
+`PATCH` versions will be reset to zero. Twilio understands that this can be very
+disruptive, so we will only introduce this type of breaking change when
+absolutely necessary. New `MAJOR` versions will be communicated in advance with
+`Release Candidates` and a schedule.
 
 ## Supported Versions
 
-`twilio-node` follows an evergreen model of support.  New features and 
-functionality will only be added to the current version.  The current version - 
-1 will continue to be supported with bugfixes and security updates, but no new 
+`twilio-node` follows an evergreen model of support. New features and
+functionality will only be added to the current version. The current version -
+1 will continue to be supported with bug fixes and security updates, but no new
 features.
 
-## Edge Features (alpha Branch)
-
-Twilio frequently rolls out new features in public and private beta periods.
-Twilio strives to ship early and often and bake customer feedback back into our 
-products.  To support that mission, the `twilio-node` helper library has an 
-`Edge` version based of the `alpha` branch.  This version is identified with an
-`alpha` metadata tag on the version number.
-
-The way the `Edge` artifact is created is by playing the `Edge` features on top
-of our stable artifact.  The `Edge` artifact will always have the same version 
-number as the stable artifact it was created from, but with an `alpha` suffix.
-
-For example, `3.0.0-alpha-1` is the `3.0.0` branch with `Edge` features included.
-If there is a change to one of the `Edge` features we may regenerate the `Edge`
-artifact and release a new `3.0.0-alpha-2`, new `Edge` artifacts simply increment
-the number after the `alpha` suffix.  All `Edge` features are considered 
-unstable and a backwards incompatible change in an `Edge` feature will not cause
-any version change so you should take care when upgrading from one `alpha` 
-version to another.  
-
-Once an `Edge` feature has matured it will be considered `Mainline` and included
-in the stable artifact, with a `MAJOR` or `MINOR` version bump.
-
-To use an `Edge` artifact in your NODE project you will have to make sure that 
-you pin the artifact with `alpha` stability in your `package.json`.
-
-[semver]: http://semver.org/
-
+[semver]: http://semver.org/
diff --git a/lib/rest/Accounts.js b/lib/rest/Accounts.js
@@ -1,5 +1,14 @@
 'use strict';
 
+/* jshint ignore:start */
+/**
+ * This code was generated by
+ * \ / _    _  _|   _  _
+ *  | (_)\/(_)(_|\/| |(/_  v1.0.0
+ *       /       /
+ */
+/* jshint ignore:end */
+
 var _ = require('lodash');  /* jshint ignore:line */
 var Domain = require('../base/Domain');  /* jshint ignore:line */
 var V1 = require('./accounts/V1');  /* jshint ignore:line */

diff --git a/lib/rest/Api.js b/lib/rest/Api.js
@@ -1,5 +1,14 @@
 'use strict';
 
+/* jshint ignore:start */
+/**
+ * This code was generated by
+ * \ / _    _  _|   _  _
+ *  | (_)\/(_)(_|\/| |(/_  v1.0.0
+ *       /       /
+ */
+/* jshint ignore:end */
+
 var _ = require('lodash');  /* jshint ignore:line */
 var Domain = require('../base/Domain');  /* jshint ignore:line */
 var V2010 = require('./api/V2010');  /* jshint ignore:line */

diff --git a/lib/rest/Chat.js b/lib/rest/Chat.js
@@ -1,5 +1,14 @@
 'use strict';
 
+/* jshint ignore:start */
+/**
+ * This code was generated by
+ * \ / _    _  _|   _  _
+ *  | (_)\/(_)(_|\/| |(/_  v1.0.0
+ *       /       /
+ */
+/* jshint ignore:end */
+
 var _ = require('lodash');  /* jshint ignore:line */
 var Domain = require('../base/Domain');  /* jshint ignore:line */
 var V1 = require('./chat/V1');  /* jshint ignore:line */