This is a VERY ALPHA port of the Node.ACS API for node.js projects hosted outside Node.ACS. I am not even sure if this will work yet. USE AT YOUR OWN RISK!





GitHub Stars



Last Commit

8yrs ago






Size (min+gzip)




Type Definitions





Appcelerator Cloud Services (ACS) API

This is a VERY ALPHA port of the Node.ACS API for node.js projects hosted outside Node.ACS. I am not even sure if this will work yet. USE AT YOUR OWN RISK!


$ npm install acs-api


Require the 'acs' library in your app:

var ACS = require('acs-api');

Initialize the 'acs' module with your ACS OAuth credentials.

ACS.init('<OAuth key>', '<OAuth secret>');

This only needs to be done once, and is typically done in the main app.js script file.

Using the ACS APIs

Now let's use ACS in a Node.ACS application, we'll query all available places in the ACS app and return through response:

var ACS = require('acs-api');
ACS.init('<OAuth key>', '<OAuth secret>');

function queryAllPlaces(req, res) {
        page: 1,
        per_page: 20,
        where: {
            lnglat: { '$nearSphere': [-122.23, 37.12], '$maxDistance': 0.00126 }
    }, function(data) {
        if(data.success) {
        } else {
                'Error occured. Error code: ' + data.error + '. Message: ' + data.message);

User Login Session Management

Most of ACS APIs require a user to be logged in, so it is important to have a way to manage user sessions in your Node.ACS application. Node.ACS provides two ways of managing ACS login sessions in a Node.ACS application:

Cookie-based. With cookie-based session management, most of the management is done for you. Manual. Allows you to manage your own login sessions. These methods are described in the following sections.

Cookie-Based Session Management Cookies are frequently used by ACS applications to store session information and pass it between client and server. ACS cookies can be used with Node.ACS as well. To enable cookies to be passed through between the client and ACS, pass in the HTTP request and response objects as parameters when making an ACS API call. For example:

function loginUser(req, res) {
        login: 'test', 
        password: 'test'
    }, function(data) {
        res.send('User logged in!');
    }, req, res);

The ACS library retrieves the session ID from the request's cookies. If a _session_id cookie is present, it uses that session ID to make the ACS API call. If not, it performs a regular API call without session information.

If a session ID is returned in the ACS API response (for example, users/login.json), the session information is added into the response object. Specifically, it adds a Set-Cookie header to pass back the Node.ACS project's client.


The ACS library sets the cookie header in the response object, which must be done before sending any response data (for example, by calling the response object's send method). If you send any response data before the ACS API callback function is invoked, the ACS library will throw an exception when it tries to set the cookie headers, with a message like, "Can't render headers after they are sent to the client." Session information is stored in a cookie named _session_id. You can also manually set this session ID cookie on the client side. For example, if you are calling your Node.ACS service from a Titanium application that uses ACS directly, you can retrieve the active session ID from the Titanium.Cloud.sessionId property, and adding a Set-Cookie header when making a request to the Node.ACS service. Manual Session Management An ACS user login session is identified by a session_id parameter in the request or response data. When logging in to a user account or creating a new user, the session_id is returned in the response data of the API calls. It can be retrieved from the response data by using data.meta.session_id. For example:

function loginUser(req, res) {
        login: 'test', 
        password: 'test'
    }, function(data) {
        res.send('Login session is: ' + data.meta.session_id);

To reuse this session for making other API calls, pass it in as part of the request data (sessionid: _stored_session_id). This gives you full control of the sessions, you can store the session in any ways and reuse them anytime (as long as the session is not expired on ACS server) later for making API calls. For example:

function createPlace(req, res) {
        name: 'test', 
        city: 'city_name', 
        session_id: '<stored session_id>'
    }, function(data) {
        res.send('New place created!');

Create the foo module project in current dir.

Appcelerator Titanium License

Appcelerator Titanium is Copyright (c) 2009-2010 by Appcelerator, Inc. and licensed under the Apache Public License (version 2)

acs-api license

Apache Public License (version 2)

Copyright [2013][Daniel Mahon <daniel@mahonstudios.com>]

Licensed under the Apache License, Version 2.0 (the "License"); you may not use this file except in compliance with the License. You may obtain a copy of the License at


Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.

Rate & Review

Great Documentation0
Easy to Use0
Highly Customizable0
Bleeding Edge0
Responsive Maintainers0
Poor Documentation0
Hard to Use0
Unwelcoming Community0
No reviews found
Be the first to rate


No alternatives found


No tutorials found
Add a tutorial