Announcements, Preview

Our spin-off project Datawaki is now public

You might have been wondering what teowaki has been up to, since it’s been a while after our last post. It turns out we had a very busy May and June, speaking at conferences in Berlin, Barcelona, Kiev, Tel Aviv and London, and attending a few other conferences, including Google I/O in San Francisco.

Every time I talked to other developers and told them about our internal analytics solution —based in Big Query and Redis— I could see a lot of interest. And some even asked me if they could use it for their own projects. So we decided to extract that functionality out of teowaki, prepare it for public use, and make a spin-off project. I’m proud to say Datawaki is now  live.

With Datawaki you can analyse anything and everything going on in your application. You only need to provide a JSON with the relevant fields for your business, and Datawaki will take care of storing it, sending real-time alerts via e-mail on important events, providing timely reports and allowing you to run interactive queries at any time. Over billions of rows. In a few seconds.

You don’t need to worry about storage, backups or allocating development resources. Just send us your events and we’ll do the rest.

As of today you can only register if you are using Heroku. We will get the JSON directly from your log file, so integration is very easy on your end. We will provide a public REST API in the future so anyone can manage their events with Datawaki.

This is just the beginning. We are now waiting for your feedback to know what you want, so we can make Datawaki better and brighter for you all.  If you are a Heroku user and would like to give Datawaki a try, please send us an e-mail to and we will invite you over.

Announcements, Development

teowaki Developers Centre

You have heard me say —probably many times— teowaki has a nice, usable, RESTful API. But you had to trust me on that, because we hadn’t had the time to document it properly.

From today you don’t need to trust me anymore, since you can play with the API by yourself following the documentation we have published at teowaki Developers Centre.

If you are already familiar with REST, you can proceed directly to our API overview, or to our hypermedia documentation. If you want to know more about REST you can try the REST basic concepts tutorial. And if you like APIs, you probably want to take a look at our Developer Tools section.

A few examples from our API using cURL from the command line:

Get the public contents about redis
curl -H "accept:application/json"

Get the profile of the user Ada
curl -H "accept:application/json" ""

Or directly from your browser:

If you want to access private contents, you will need to Authenticate using OAuth2 first. But with the OAuth2 intro in the Developers Centre that should be a breeze.

Give it a try, and tell us about all the awesome things you are building with it at or @teowaki. We will feature in our blog the coolest uses of the API.


Finalists at Startup in Action, Rome

I was in the middle of a G+ hangout with Diego yesterday, when the subject of an incoming email got my eye. I could hardly believe it. teowaki had been selected as a finalist for the Startup in Action contest.

In their own words, Startup in Action is “a great opportunity for hi-tech Startups to be known by programmers, engineers, Italian ICT companies and large international companies which will attend to Codemotion Rome”.

It turns out Codemotion is one of my favourite events, and I was already very happy because I had been confirmed as a speaker a few weeks ago. So you can imagine our excitement when we received the news from Startup in Action.

Diego will be joining me at Codemotion Rome, where we will have a mini-stand for teowaki. We hope to hold a lot of interesting discussions and we are looking forward to knowing what Italian developers think of our product.

If you are attending Codemotion Rome, please come say hi to our stand. We’ll be happy to see you… and if you are good we might even give you some sweets!


How can I help you?

We work hard to make teowaki easy to use. But still, sometimes people ask me questions about teowaki. Things that are not really obvious, like “Do I need to pay to use teowaki?” or “with all the collaboration tools out there, why did you decide to build a new one?”.

To answer those questions —and many more— we just launched our Help Centre . At the moment we have a few entries about what is teowaki, how the notifications work, how to use your account settings, what integrations are available and general details about payments and price plans.

We will be adding more sections in the next weeks. If you think there is something important missing, please contact and let us know.

Announcements, Development

Announcing our engineering blog

Teowaki is a tool for developers. And it’s done by developers. So it was the high time to start writing about the technology that powers teowaki. I am proud to announce today teowaki’s engineering blog.

In the first post Diego tells us how he upgrades our servers with Ansible. Stay tuned for insights, tricks and new posts on how we use NoSQL, big data, AngularJS, hypermedia APIs, cloud services and everything that keeps teowaki up and running.

We hope you will enjoy our new blog as much as we enjoy writing it.

If you have any suggestions for new articles or you want to be featured as a guest engineer please write us at

Announcements, Development

Get hooked to the web

The internet is a busy place. As a developer you need to check a lot of services to know what’s going on with your teams. Has anyone pushed new changes to my repositories? Did my boss enter any new tasks for me? Have my latest changes broken the build? Keeping up to date is time consuming. Wouldn’t it be great to see all your updates on a single feed? We thought so.

Yesterday we released teowaki’s webhooks. You can listen to events happening elsewhere in the internet and show them in your team stream. Click on an event to see the details or navigate directly to the page where the event happened. You can even use teowaki’s to search through your received webhooks.


You don’t need to do anything special to start receiving webhooks. All you need is your team’s secret URL. Go to the list of teams and click on the team settings icon of any team you admin. You will notice a new section called Webhooks. In that section you will find a secret URL for your project, such as


At the moment we have integrated GitHub, Pivotal Tracker and Bitbucket.  Here is what you need to configure on those tools to send webhooks into teowaki:


Go to your project settings and navigate to the Settings menu. Select the Webhooks & Services option and simply paste your teowaki’s secret URL into the Payload URL input box*.



Click on the Settings icon of your project and then select the Hooks option. From the dropdown list of integrations choose POST and simply paste your teowaki’s secret URL into the URL input box.


Pivotal Tracker

Select Configure integrations from the Project menu. Scroll down to the Activity Web Hook section and simply paste your teowaki’s secret URL into the input box.


Getting Hooks from any other service

If you want to send webhooks into your project from any other service, all you need to do is POST a XML, JSON or x-www-form-urlencoded request to your secret endpoint. The POST should include at least a field called name and a field called description. You can also send a field called url and a field called origin_name. As long as your POST contains those field, teowaki will display the information into your team stream.

The use cases for custom webhooks are endless.  As an idea, you can send webhooks from scripts running in your servers every time a new version is deployed or a service is restarted. Everybody in your team will receive the notification on teowaki.

Future integrations

We are already working on integrations for Jira and Trello. We will keep adding new services we think are interesting for developers. If you are using teowaki and you are missing any integrations, please let us know.

For any suggestions or any questions you might have, we are always available at

* at the moment we only recognise GitHub push events. We will be adding more GitHub events in the following weeks