0.0.6 • Public • Published

JavaScript Carvoyant API

The JavaScript Carvoyant API for both the browser and Node.js. This library was created using the Carvoyant API Reference and as of writing this, this library has complete feature parity with the documented Carvoyant API Reference.

Release Notes

  • 0.0.7 (TBD) - Cleanup the API
    • Go to event-based model for all APIs to get away from callback hell
    • Stop passing each API argument as a function argument (use function (options, cb))
    • Refactor out of single client.js into more specific modules
    • Implement code coverage in the tests
  • 0.0.6 (2014 May 8) - 0.0.5 Follow Up
    • Marked constraint APIs as deprecated (No warning when using, just code/documentation level)
    • Added Client constructor API documentation (Including deprecation markers for API Key and Security Token)
    • Added deleteVehicle API (Known Issue: Deleting a vehicle with any data will fail)
    • Removed constraint related Known Issues since the APIs are deprecated
  • 0.0.5 (2014 May 6) - Added support for OAuth authentication/authorization
    • No API changes
    • Previous Basic Auth (API Key and Security Token) support works as it did before
  • 0.0.4 (2014 Mar 11) - Add support for missing Carvoyant APIs
  • 0.0.3 (2014 Mar 8) - Bugfix release
  • 0.0.2 (2013 Nov 26) - Miscellaneous minor refactorings
  • 0.0.1 (2013 Nov 19) - Initial release

Known API Issues

Below are a list of known (as of this writing) issues/inconsistencies with the upstream Carvoyant API:

  • No API to create trip data (Makes sense but this has an impact on testing)
  • No API to create/update/delete constraints (Has an impact on testing and API completeness)
  • No API to create event notifications (Makes sense but has an impact on testing)
  • Some list APIs return plural form (subscriptions, notifications) while the rest do not (This is just an inconsistency that might cause you issues in using the API without knowing)
  • client.deleteVehicle is implemented but the backend will not allow you to delete a vehicle with any data. This means that while the API is there, it will likely fail until Carvoyant's APIs support it.


Below are usage scenarios for both the browser and Node.js.


Browser support for the JavaScript Carvoyant API is provided by browserify. This offers a zero configuration deployment, meaning you do not need to download/install third party dependencies to get this library to work in a web browser. While using this library will be no different than usual, there are two versions of the file:

Installation can be as simple as downloading the proper JavaScript file into your project or installing it via Bower which is as simple as installing any other browser component using Bower:

bower install carvoyant --save

Now that you've installed it into your project, here is an example HTML snippet to get you started:

<!-- ... -->
<script src="bower_components/carvoyant/carvoyant.js"></script>
<!-- <script src="bower_components/carvoyant/carvoyant.min.js"></script> -->
// New style authentication/authorization
var client = carvoyant.createClient({accessToken: '...'});
// Old style authentication/authorization
// var client = carvoyant.createClient({apiKey: '...', securityToken: '...'});
<!-- ... -->


Installation is as simple as any other Node.js module using NPM:

npm install carvoyant --save

At this point, you can use the module like any other:

// New style authentication/authorization
var client = require('carvoyant').createClient({accessToken: '...'});
// Old (deprecated) style authentication/authorization
// var client = require('carvoyant').createClient({apiKey: '...', securityToken: '...'});

For more details on what APIs are available and how to use them, please use the source until I can get the items listed at the bottom of the page complete.

Client Configuration

Below is a list of client configuration options:

  • accessToken (required if using OAuth): This is the OAuth access token (0.0.5+)
  • apiKey (required if not using OAuth): (deprecated) This is the API Key (This support will be phased out by Carvoyant)
  • securityToken (required if not using OAuth): (deprecated) This is the Security Token (This support will be phased out by Carvoyant)
  • apiUrl (optional): This is the URL to use for the Carvoyant API


As of 0.0.5, the preferred way to interact with the Carvoyant API is OAuth. The Carvoyant JavaScript API does not provide any of the OAuth facilities and requires you to give it an OAuth access token. The reason for this is that real OAuth typically has a user driven portion and for a JavaScript API, there's no guarantee that there will be facilities to support this process. For example, there is no bundled server component that would function as an OAuth callback to exchange an auth code for an access token. Even if there was, there'd be no way to ship that in the browser, a feature I've worked very hard to make possible.

All of that being said, you are responsible for obtaining the OAuth access token. The way I do this for development is I created a Carvoyant Application and using that application, I will request an access token in the browser using a URL like this:{applicationKey}&response_type=token&redirect_uri=noredirect. This URL will prompt you for your Carvoyant user credentials and once you successfully provide them, a nice UI will display giving you your access token. I will then put that in my test/client_config.js to run the test suite. It's not ideal but this also isn't something that needs to be done a lot. It's also not something I can control.

Of course, for a real world application with a server-side component, you could do the full OAuth handshake process to do this in a more secure fashion. For more details on the OAuth implementation for the Carvoyant API, please view the Carvoyant OAuth Documentation.


This project uses best of breed libraries and tooling:

  • Browserify - Tool for allowing you to write browser code like Node.js
  • Grunt - The JavaScript task runner
  • Karma: Test runner for JavaScript
  • Lodash - Utility library for JavaScript (We're current piecing together the pieces we need instead of using the whole library to make the browser builds as small as possible)
  • Superagent - JavaScript AJAX library for the browser and Node.js

Running Tests and Building

Right now the default Grunt command will run all tests (browser and Node.js) and create browser binaries for the project. To do this, all you have to do is run grunt from the command line, this of course assumes you installed the project dependencies after cloning the repository using npm install and that you've created a working test/client_config.js. (You can do this by copying test/client_config.js.tmpl to test/client_config.js and updating accordingly) As of this time, unit tests and integration tests run together, there is no separation. Do to the nature of the upstream Carvoyant API, this can leave behind created vehicles. You can clean these up from the Carvoyant Dashboard.


The way tests currently work right now is we create a vehicle and that vehicle is used for all tests where possible. Any write API we test will be against the created vehicle. We will never update an object we did not create as a part of our test. When you are done, the created vehicle will be left in your inventory due to a missing delete API.

There are a few tests that require us to use a vehicle id that already has data associated with it, due to us not having APIs to create the data behind the APIs being tested. These cases are documented and handled in the test/client_config.js.

API Documentation

You can also generate JSDoc documentation using grunt jsdoc. (This will eventually be incorporated into the build/release cycle so we can host the API documentation online.)



Package Sidebar


npm i carvoyant

Weekly Downloads






Last publish


  • whitlockjc