Managing Lights and Plugs Made Easy for Developers With Taapi’s API

“…Taapi is gamification at it’s best.” Wired 
“The game is the first global, mobile gaming platform that will have a significant impact on the real-world.”

Taapi provides the first, open-source, global, all-purpose energy management API for developers.  

We believe that users should be able to control their light and wall sockets from their favorite applications and that app developers and game builders should be able to incorporate light and wall socket controls into their applications.
Managing lights and plugs has typically been an expensive, proprietary domain using closed source systems. Producers of light and wallsocket controllers do not allow wide developer access to their products in the home or integration of their in-home products with third-party applications.

How Taapi Works
We build wallsocket adapters and smart lightbulbs that operate using a commercial-grade protocol and low-energy WiFi chipset.
Through our smart bulbs and wall socket adpaters we create secure communication between lights and wall sockets to power lights and sockets on and turn them off.
The Taapi systems handle authentication of users devices, auth of user ID’s in your apps via OAuth and creating a completely masked identity for a user’s devices for security.
Taapi also maintains a constant record of state that recalls the state a socket or light was in when it was acted upon by Taapi. Maintaining states ensures that the light or wall socket can be returned to it’s original state when a user wants to regain full control of their lights or wall sockets.

Taapi employs commercial-grade standards in it’s open-source APIs.

Multiple devices can be run off of a Taapi wallsocket.  Lightbulbs can be used for hardwired lights, like overheads.

Taapi creates local WiFi communication between sockets and bulbs by using a hub that connects to your router. The hub communicates securely with the Taapi service and the light’s owner. The Taapi service exposes REST services to developers.

Taapi Cloud Services for Developers

The Taapi Cloud and Service Paths

Easy Integration for iOS, Android and OUYA Enabled Games

Integration with Taapi is optimized for speed and ease of set-up.
Libraries for iOS, Android and a rapid-setup, special build set of classes for OUYA will be available to developers. Integration with Taapi is optimized for speed and ease of set-up.

The Taapi Social Game
The Taapi API is now used to power a social game where unused lights are added to a pool of anonymous lights waiting to be turned off. Players race to turn off lights as they are added to the pool. This game leverages many parts of the API such as session establishment, auth and lights and plug management.
The first Taapi game is available on iOS, Android and the OUYA game console.

The Taapi Social Game

What will the Taapi API offer developers?
Taapi manages the heavy lifting that devs typically associate with environmental controls: hardware, normalization, security, WiFi protocols and local network authentication
We manage those pain points and provide the dev with a manageable API that they can leverage as the dev, and their users, see fit.
Taapi has tools to provide access to a range of game and app developers by providing a full REST API with hooks that can programmatically act on Taapi’s services from your app or service.
The Taapi API will provide access for app and game devs to features such as:

  • Adding new players
  • Authenticating players
  • Calling player stats
  • Calling general country, energy, and date stats
  • Initiating a race session
  • Obtaining the stats for a unique race session
  • Polling for available races

Taapi has selected Atlassian ( products for community support, Mashery ( for API hosting and Taapi has built-in an OpenSocial container for developers to write gadgets for Taapi using the OpenSocial ( standard.

Taapi’s OpenSocial container support will allow developers to quickly and easily write OpenSocial compliant gadgets that can call and serve a number of Taapi features like public Taapi use statistics, aggregated stats, individual users stats and game session availability.

The Taapi OpenSocial container will support gadget authentication via OAuth to enable personalized, contextual player information and interaction as well.  Players will be able to add approved gadgets to their instances of the Taapi game and extend Taapi’s functionality.
For example, a developer could write a ‘My Country’ Taapi gadget to alert a player when a session in a specific country is available, authenticate them, opt them into the game session and tweet about their participation, all in that country’s native language(s).

Taapi founder Carol Glennon states, “Support for an accelerated development process was one of our top goals for the Taapi platform. Enabling gadgets through our OpenSocial container makes it easy for developers to gain fast access to our API while writing cool gadgets that users can use in Taapi right away.”

Access to the Taapi API will also be available on Zapier, a service that syncs many different web apps. A developer can use Taapi and Zapier to initiate a number of web actions for example, setting a block of time that lights should be turned off for a user when they schedule a calendar event in the devs application.

Taapi Partners and Community Services for Developers

We Are Counting on YOU
We need your support as a backer now to produce the lightbulbs and wallsockets that will be used in thousands of your users homes and offices.
Enabling us to produce our home kits provides you as a developer with an ever-widing pool of users that are ready to use Taapi with your app and games.

Please come and back us today and pick a great reward. It’s inexpensive, fast and will benefit your app or game greatly.

Taapi Team Experience
The Taapi core executive team have been working on projects together for over a decade and have experienced amazing success in that time. Together, they have a pretty cool history of ability to deliver amazing experiences. Examples of previous work includes delivering mobile apps, games as well as cutting edge and complex 3D animations and solutions for major consumer-focused companies including Time Warner, Intel, CBS, California Tourism, Delta Airlines and National Geographic.

We have been recognized and received over a dozen National and International awards for our work and have been at the cutting edge of technology for a combined four decades.

2012 National Geographic Kids Almanac
2011 Visit California iPad application
2011 San Francisco Giants and Safeway2011 San Francisco Giants and Safeway
2011 MLB, 7Eleven and Frito Lay
2010 Stevie award – Most Innovative Company  of the Year
2010 World Cup through FIFA backed 1Goal
2004 Who Wants To Be A Millionaire U.K. (mBlox)

Author: Carol Glennon

OpenSocial Overview, part 2

The OpenSocial gadgets specification includes multiple APIs that make it easy to authenticate users and access data and core functions on participating social networks. We featured an OpenSocial infographic here as part of our two-part shout out to the folks at OSCON.
Platforms that have OpenSocial compliant application containers can run OpenSocial gadgets, sometimes called ‘plug-ins’. Some of the companies that support OpenSocial plugins in their public environments are: Atlassian (known for JIRA, Confluence and other great systems), SAP, IBM,, SugarCRM, Yahoo!, Google and many more. These platforms run Apache Shindig to create the container that supports OpenSocial gadgets. The evolution of Shindig is Apache Rave. See the end of this post for more on Apache Shindig and Rave.

This sample will demonstrate a sample of a formed XML gadget descriptor and a live-test. Every gadget is made up of an XML descriptor that calls on functions that the Apache Shindig server supports.

Step 1. get the sample.
In this example we give you a sample XML gadget descriptor here: XML Gadget Descriptor. Download and save it if you want to try the test yourself and have a code sample to alter later.
The main function areas of this sample are: module prefs, user prefs, get and display. The entire OpenSocial gadget specification is here. (Updated, now 2.5)
This sample calls and displays a feed of news articles and relies upon the function.

Step 2. decide to host the sample or use our URL.
Either download the XML sample and place it on a publicly accessible URL of your own or use our URL in step 4 of the demo.

Step 3.  test the sample live.
Testing your XML Gadget descriptor is important.
Yahoo! has a sandbox for live OpenSocial plug-ins and it only takes a couple of minutes to set-up. Head to and sign up for a dev account, don’t worry-it’s free.
Log in and head to “My Projects”, select “New Project”, choose type “YAP” (Yahoo! Application Project), select “Import New XML”.
Either paste in your own URL that points to the XML sample you downloaded in Step 1. or point to our sample URL, select “Import”.

Step 4. Preview the sample.
Select “Preview” to view the sample as a formed gadget. This is how your gadget will look for users.

A couple of notes about testing with the Yahoo! live sandbox, Yahoo requires a category parameter and value in the module preferences. Without the category parameter the descriptor will generate errors.  You can remove this parameter after testing if need be.

 title="Google Gadget Dev News"

Here is an example of this OpenSocial example gadget in the SAP StreamWork application.

Example gadget in SAP Streamwork application

You can use OpenSocial to deliver many types of social data to your users quickly and easily as well as authenticate them for interactions with social data. Customizations and functions for the OpenSocial standard are extensive and growing.

Here are a few ways that you can get started:

View a tutorial.

Become  an “OpenSocial container” by using Apache Rave to host social apps.

Contribute to the evolution of the OpenSocial specification or become an OpenSocial Foundation member.

Follow @opensocial.

Author Carol Glennon

OpenSocial Overview, part 1

The OpenSocial gadget specification includes multiple APIs for social software applications to easily authenticate users and access data and core functions on participating social networks. Read Part 2 of the series to follow an OpenSocial tutorial and do a live test of a working gadget.
This infographic shows the evolution of the OpenSocial standard and supporting server-side technologies.

The evolution of the OpenSocial standard.

Author Carol Glennon