AT&T M2X Javascript Library
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
dist
examples
src
.gitignore
CONTRIBUTING.md
LICENSE
README.md
docs.md

README.md

AT&T's M2X Javascript Client

AT&T M2X is a cloud-based fully managed time-series data storage service for network connected machine-to-machine (M2M) devices and the Internet of Things (IoT).

The AT&T M2X API provides all the needed operations and methods to connect your devices to AT&T's M2X service. This library aims to provide a simple wrapper to interact with the AT&T M2X API. Refer to the Glossary of Terms to understand the nomenclature used throughout this documentation.

Getting Started

  1. Signup for an M2X Account.
  2. Obtain your Master Key from the Master Keys tab of your Account Settings screen.
  3. Create your first Device and copy its Device ID.
  4. Review the M2X API Documentation.

Compatibility

Currently, the M2X Javascript client is supported on all modern browsers except IE8 and IE9.

Usage

M2X Class

The main object encapsulating all API functionality is the global variable M2X. In order to create a M2X object you will need an API key, which can be either a Master Key or a key belonging to a specific device (in which case you will only be allowed to read/write to this device).

The following is a short example on how to instantiate an M2X object:

var m2x = new M2X("<API-KEY>");

The M2X object also provides a simple method for checking the API status (so if you are having connectivity issues, you can check whether the API is currently down):

m2x.status(function(data) {
    console.log(data);
});

Every method receives an extra callback for handling errors, it will be called if an error occurs with relevant information:

m2x.status(function(data) {
    console.log(data);
}, function(error) {
    console.log("Oops, the API cannot be reached: ", error);
});

An M2X object provides methods for communicating with the remote API. Methods are organized under the following modules: keys, devices, charts and distributions.

  • Distributions

    m2x.distributions.view("<DISTRIBUTION-ID>", function(distribution) {
        console.log(distribution);
    }, function(error) {
        if (error.statusCode === 404) {
            console.log("The distribution does not exist.");
        } else {
            // Something else happened, let the user know.
            console.log(error);
        }
    });
    
    m2x.distributions.list(function(distributions) {
        console.log(distributions);
    }, function(error) { console.log(error); });
    
    m2x.distributions.create({name: "distribution name", visibility: "private"}, function(distribution) {
        console.log(distribution);
    }, function(error) { console.log(error); });
  • Devices

    m2x.devices.view("<DEVICE-ID>", function(device) {
        console.log(device);
    }, function(error) { console.log(error); });
    
    m2x.devices.list(function(devices) {
        console.log(devices);
    }, function(error) { console.log(error); });
    
    m2x.devices.create({name: "device name", visibility: "private"}, function(device) {
        console.log(device);
    }, function(error) { console.log(error); });
    
    var xhr = m2x.devices.valuesExport("<DEVICE-ID>", {streams: "<STREAM-ID>"}, function() {
        console.log("Job Location", xhr.getResponseHeader("Location"))
    });
  • Keys

    m2x.keys.view("<KEY-TOKEN>", function(key) {
        console.log(key);
    }, function(error) { console.log(error); });
    
    m2x.keys.list(function(keys) {
        console.log(keys);
    }, function(error) { console.log(error); });
    
    m2x.keys.create({device: "<DEVICE-ID>", name: "key name", permissions: ["GET"]}, function(key) {
        console.log(key);
    }, function(error) { console.log(error); });

Refer to the documentation on each class for further usage instructions.

Versioning

This library aims to adhere to Semantic Versioning 2.0.0. As a summary, given a version number MAJOR.MINOR.PATCH:

  1. MAJOR will increment when backwards-incompatible changes are introduced to the client.
  2. MINOR will increment when backwards-compatible functionality is added.
  3. PATCH will increment with backwards-compatible bug fixes.

Additional labels for pre-release and build metadata are available as extensions to the MAJOR.MINOR.PATCH format.

Note: the client version does not necessarily reflect the version used in the AT&T M2X API.

Example

There's an example included in the examples/ directory.

Building from Source Code

The source code for this library is located in the src/ directory. For better organization and loading of modules we use the AMD API. Using a small replacement of require.js called almond the source is then build into a single distributable file (non-AMD) to make distribution and usage easier.

In order to build this library you will need two things (almond comes included in this repo inside the dist/directory):

Once you have these installed go to the dist/ directory and run ./build.sh (make sure the script has execute permissions). If everything goes well you should now have a minified file named m2x-VERSION.min.js file and a non-minified version named m2x-VERSION.js inside the dist directory.

Common Errors

If you need help handling errors within the required libraries, please check out these helpful resources:

License

This software is provided under the MIT license. See LICENSE for the terms.

Acknowledgements

This client is a direct port of Leandro Lopez' AT&T M2X client for Ruby so all the credit should go to him.