All notable changes to this project will be documented in this file.
- Fix a few issues in the README documentation (#73)
- Allow
subject
andbody
to be overridden independent offrom
for transactional messages (#75)
- Fix an issue calculating the content length of multi-byte utf-8 string characters (#69)
-
(BREAKING) Remove the dependency on
request
(#62)- We don't expect this to break many consumers of
customerio-node
. Unless you were usingrequest
specific options, you don't need to make any changes.
- We don't expect this to break many consumers of
-
(BREAKING) Return an
Error
instance for non-2XX
status codes (#62)- We don't expect this to break many consumers of
customerio-node
. Unless you were usinginstanceof
to check the type of error returned from track or api methods, you don't need to make any changed.message
,statusCode
,response
, andbody
are still accessible as properties on the error.
- We don't expect this to break many consumers of
-
(BREAKING)
trackAnonymous
now requires ananonymous_id
and cannot trigger campaigns. If you previously used anonymous events to trigger campaigns, you can still do so directly through the API. We now refer to anonymous events that trigger campaigns as "invite events". -
(BREAKING) Restructure the package to have a single entry point, rather than three. This is more of a standard package structure, and is more future-proof. (#63)
-
Return a readable message when the server returns an array of errors instead of
Unknown error
(#62)
- Fix exported typings for folks using
customerio-node
with Typescript (#56)
- Upgrade
ini
from 1.3.5 to 1.3.8 (#36)
- Convert
customerio-node
to Typescript (#49)
- (Breaking) Move triggerBroadcast method from Track to API class (#46)
- Support for the EU region
- Support for the Transactional API
addToSegment
andremoveFromSegment
methods
- IDs in the URLs are now escaped.
- Improved validations for data that's passed in.
- Catch scenarios where a response body is unexpectedly
null
(#25)
- Add missing API params to
triggerBroadcast
(#19) - Further improve the
triggerBroadcast
API call and catch additional params (#20) - Switch from Travis CI to Circle CI (#21)
- New API calls for manual segments (
addToSegment
,removeFromSegment
) (#16)
- New API call for adding and removing devices from push notifications (#14)
- Huge thanks to @jescalan for his work in modernizing the Javascript to es6 along with updating dependencies. (#13)
- README now has the correct Travis-CI badge
- README has standardized and expanded examples (#10)
- Fixed link in README to official Customer.io API docs
- Cleaned up .gitignore by removing unnecessary ignore statements
- This CHANGELOG file along with historical changes to provide better transparancy to changes made to the library
- New API call for API triggered broadcasts
- Added a test for the new call
- Added an example for the new call to README and examples/ dir
- An example config file for the practical examples
- Travis-CI builds now use currently maintained LTS versions of Node.JS (6, 8, 9)
- .gitkeep files no longer necessary to preserve directories
0.2.0 - 2015-07-22
- url.resolve() removed from API calls
0.1.0 - 2015-07-22
- Initial API client library
- Create Identify call
- Create Track call
- Create Track Page View call
- Create Customer Delete call
- Test suite for API calls
- HTTP Request middleware
- Create request handler with RSVP.js
- Create options method for unifying all request calls
- Create POST request
- Create PUT request
- Create DELETE request
- Test suite for middleware