Inquire about Speaking

First round speaker proposals are due April 30th, and second round proposals are due August 15th! We consider all proposals during both deadlines.

We approve more panel proposals than we do solo talks. If you are proposing a panel talk, you can list prospective or confirmed panelists you have relationships with.

  • Free (unsponsored) solo talks should only mention your technology on the first or last presentation slide, unless otherwise discussed with DataWeek (it should not be an advertisement for your technology)
  • The most popular sessions at DataWeek + API World tend to be either technical workshops (learning to build or implement something) or a “big idea” visionary talk on the future of an industry.

Preview of API World Conference Talks

Why Publishers Should Care About Wearables, And How They Can Prepare


Everyone is talking about wearable tech and Internet-connected or “smart” devices. And rightfully so. According to the research firm Canalys, the market is expected to triple in size next year alone based on mainstream consumer adoption.

The stakes for publishers to deliver results – whether that’s meeting a quota of articles shared or acquiring a steady stream of new readers – is at an all-time high. Now the publishing business, already complicated, is even more complex thanks to wearables. So what’s next?

This is where developers come in — Paul will discuss how publishes should engage with developers through an open API. Content and data are critical to any Internet-connected device. The people creating cool, interesting, new and different experiences are not from the publishing world. Paul will explore ways to leverage open APIs as incubators of ideas.

Using Graph Databases to Power the Internet of Things

Neo Technology

Graphs are a fantastic tool for understanding complex, connected, and dynamic systems, which makes graph databases the logical choice for making sense of the vast, growing web of connected devices comprising the Internet of Things. With a graph database, you can easily understand and query the relationships between devices, networks, sensors, companies, and users. This significantly advances the ability to unveil insights on everything in the IoT, including data control and security, and facilitate real-time analytics on the complex relationships between the connected devices. This session provides a brief overview of graphs and graph databases, and how they are the optimal choice to power the IoT.

Scaling the Internet of Things

ActiveState Software

The Internet of Things is exciting and clearly arriving. The prospect of networked devices constantly communicating and responding to environmental elements promises enormous change and opportunity. However, building and scaling the backend for an IoT application is not trivial.

This presentation will discuss the challenges of scaling an IoT application and responding to continuous and highly erratic application load. Particular attention will be paid to application resiliency and cost control.

Specific elements of the presentation include:

IoT application characteristics
Building flexible and resilient back end IoT architectures
Ensuring application costs map to application value
The role of APIs in IoT applications

The Dance – APIs and Indoor Location


Your phone can tell where you are pretty well. The native location libraries use a combination of GPS and Wifi to determine where it thinks you are. That’s not good enough, though, for your phone to know specifically where you are on all 3 axes inside a building.

I’ve developed a technique that works on iPhone and Android to solve that problem. It uses the native location APIs and also native bluetooth APIs to mix location and proximity to Bluetooth beacons together to communicate with a custom backend API (Rails server). The beacons are configured using the iBeacon API specification. The backend service is a pair of servers that communicate through 2 redundant layers of APIs.

You’ll come away from this talk understanding how to work with nearly a dozen hardware and software APIs. Specifically:

  • Hardware (Bluetooth low-energy iBeacon)
  • iPhone location
  • iPhone iBeacon
  • iPhone HTTP RESTful POST and GET
  • Android location
  • Android iBeacon
  • Android HTTP RESTful POST and GET
  • MQTT pub/sub
  • Rails HTTP RESTful GET

Flexible content: The Evernote API & Wearables


In this talk, Damian will explore multiple approaches to building apps for wearable devices using the Evernote API including the implications of rendering multi format content on wearable displays.

Hear Damian’s strategy to common wearable development questions such as:
Should a wearable app connect directly to a service’s API?
Should the app communicate via a phone-based companion app?
Can the app leverage existing phone based apps?

Also come to discover the approach to displaying Evernote content: Evernote notes can be large and media-heavy, how can that possibly translate to a wearable device?

The Evernote app for the Pebble is written in C, and it talks to a companion app running on the watch, written in JavaScript, which in turn talks to the Evernote service via the Evernote API. Why would anyone do that? How well does it work? What were the roadblocks? Come to this session to find out.

No Stream Processing? No Internet-of-Things

SQLstream, Inc.

What is the Internet of Things? And why should we all care? Discussions about ways to monetize Big Data have been flaring lately, and many are ready to bet on the uprising of IoT. What most talks fail to address is, however, the supporting technology that will ultimately make the difference between success (realizing the full industrial potential), and succumbing under the hype. Without the right technology data fails to become knowledge, knowledge fails to become action and action, of course, fails to become money.

One of the conditions for success and profitability is developing a technology able to handle the infinite volume, velocity and variety of the data generated by IoT. This presentation addresses the most important question: HOW can IoT be made work?—by focusing on dissecting the potential, conditions and concerns surrounding the Internet of Things and taking a deep dive into the necessity for real-time architectures such as stream processing.

This session will cover the following:

- IoT background: what is it? What are its effects? What are the major areas for development?
- What are some of the concerns surrounding IoT implementations?
- What are the main technology requirements for IoT success? Standards, parallelism, real time

From Device Data to Decision-Making: Building a Scalable Analytics API for Sensors


Join TempoIQ CEO & Co-Founder Andrew Cronk as he outlines the unique challenges of building a sensor analytics API at Internet of Things scale. Topics covered include the unique properties of sensor data, challenges in scaling data collection and storage, patterns in sensor data reads and writes, and considerations in realtime monitoring and streaming analytics.

How APIs Empower Developers to Take on the Big Banks

Yodlee Interactive

As financial data APIs become increasingly accessible and easy to integrate, the financial industry is seeing a power shift away from traditional banking institutions to quick and nimble startups that are disrupting the way people interact with their finances. No longer do we have to write out checks or bother with bank transfers – Venmo makes peer-to-peer payments as easy as a text message. No longer do small businesses in need of capital need to spend business hours at a bank branch and risk the embarrassment of being turned down for a loan – Kabbage provides small business lending online, and in a matter of minutes.

This panel discussion, featuring various members of high-growth financial technology startups in industries ranging from lending to credit, payments, personal finance management, and even data services, will discuss how this power shift is a result of APIs allowing businesses and individuals of all sizes to access financial data that has traditionally been controlled by large, established banks. The panel will also discuss what this explosion of innovation in the non-bank sector signals for the future of finance – and what this future will look like.

Enterprise APIs for the real world

Are you planning to build REST APIs for the enterprise market? Join us for a tech talk on designing REST APIs for the real world.

Whether you’re building APIs over an existing product, or you’re designing APIs before building the product (aka API First) – you must attend this session. We’ll cover topics like API standardization, authentication & authorization, versioning, sandbox environments, reference implementations, etc. We’ll talk about all of these from a practical perspective, leaving out the fluff that you’ve heard at typical conferences. But then, this conference is different!

RAML – The Opensource Modeling Language for REST APIs

Constant Contact

In this session we’ll take a look at RAML, the RESTful API Modeling Language, designed for simplicity, reusability, and discovery. See how easy it is to get started using RAML to document your API (and keep that documentation up to date), while providing even more tools to your developers including an interactive API Console. Say goodbye to long sets of text, inconsistent formatting, and incoherent solutions, and say hello to the 21st century.

Building your APIs on the Google Cloud Platform


I’ll walk the audience through the Google Cloud endpoints platform that allows 3rd party developers to design, develop and monitor their APIs on App Engine. We will also talk about the client libraries that we provide to consume those APIs from iOS, Android and the Web.

Quantify Thyself, then Go Forth and Conquer with a Personal Life API


# Abstract
Learn what to quantify, how to automatically gather the data and then we will create a Life API to access and analyze your data.

# Session Type
Technical Workshop (90 Hour Tutorial)

# Description
Learn how to expose all your quantified self data via a simple Life API. Use that data for tasks ranging from making real-time decisions to long term planning.

The workshop is composed of the following three phases.
Phase 1: Use techniques from Personal Productivity experts to identify what data is important to quantify.

Phase 2: Create a template for helping us determine what tools, services and devices will automate (mostly) our data collection.

Phase 3: Combine and expose our data behind a Life API. We will design the API using and implement it using Python/Flask. At this point we will explore how we can use this API and put our data to work.

To focus and make sure you all walk away with a tangible result within our allotted time, we will limit our scope to the area of health.

# Tags
python, flask, api, apiary, rest, quantified self, wearables, sensors, automation, productivity, gtd

# Audience Level
- Intermediate

# Prerequisite knowledge for this session
- Python/Flask experience or equivalent

# Video from a previous talk on Personal Productivity for Developers
- Corresponding Blog post with slides:

# Tutorial Prerequisites
- Paper Pencil/Pen or digital equivalent
- Laptop with a Python/Flask local environment
- Local instance or Internet access

# Additional Notes
I can turn this workshop into a 40 minute Solo speaker presentation by removing the interactive elements.

Linked APIs: dark art of building highly distributed systems that can cross organizational boundaries

Layer 7 Technologies

Practical problems that innovative product and tech teams face increasingly go far beyond the comfortable usual. “Big Data” doesn’t just mean petabytes of data or a data-set that doesn’t fit in a single large RDBMS, anymore. A “distributed system” doesn’t just mean a clever multi-tier architecture or even an AWS deployment happily humming-along across multiple regions. Increasingly, Big Data problems mean processing data-sets the various parts of which are distributed across multiple organizations. A “distributed system” is usually one which needs to connect non-heterogenous systems across organizational boundaries. Such problems are far from trivial and require new kinds of approaches. Linked APIs architectural style is a new frontier of distributed programming and Big Data: one that can cross over organizational, technological and cultural boundaries to break through data silos to better integrate data and processes.

Are Wearables the Future of Advertising

ADOTAS — If the key to advertising is all about understanding the pulse of customers, the rapid evolution of the wearable mobile market is surely to raise the bar. Walking through this year’s CES and Mobile World Congress events, wearable computing was front-and-center, and if your initial reactions were like mine, you first were awestruck with the direction it is taking, and then wondered how best to monetize this new technology genre. The potential impact is huge with IDC estimating the global market for wearables to surge to 111.9 million units – an annual growth rate of nearly 80%. This significant upside is providing an increase in conversations we are having with brands, marketers and developers on how best to harness the future impact of wearables, and ultimately, crack the monetization code. The bottom line is wearable mobile devices are begging you to uncover what game-changing possibilities and advertising potential lie ahead. Although wearables share similarities with its smartphone sibling, they are truly distinct and provide a new and exciting medium for marketers to target loyal consumers with personalized, interactive, seamless and immersive brand experiences. There are endless possibilities and infinite unknowns for mobile advertising as advertisers explore tailoring ads for a new crop of devices aligned to its respective distinctive features. Consumers living in today’s connected world will lead the way and compel advertisers to reimagine the purview of brand engagement, user targeting and advertising at large. There is massive opportunity in the burgeoning sector as IDC expects the market to triple sales in 2014 from last year’s figures, which demands a new way of thinking and an alternative approach to how we once addressed desktop and mobile ads. In doing so, there are four significant factors that need to play out before advertising can really take hold on wearables. Form Factor: While the initial phase of wearables are simple, low-price point devices, e.g. Jawbone UP, Nike+ FuelBand and Fitbit, without the digital real estate to utilize more traditional digital ad formats, the opportunities offered shouldn’t be discounted. For example, their complimentary apps provide a springboard for potential monetization options, such as corresponding partnerships to be served up as rewards for achieving certain tasks or native ads tied into the overall user experience. But other more sophisticated, next generation category devices such as eye-led wearables, like Google Glass, and smart watches, such as the Samsung Galaxy Gear, offer even more opportunity. While Google has been vocal about ads staying off Glass, as demand increases and adoption of pursues, there will be plenty of conversation around monetization and ads serving as prime vehicles for revenue. Operating System: Opportunity breeds competition so expect another front for the operating system battle to take off. With no clear winner leading the way currently, expect the wearable OS market to stay fragmented as more players enter the market. As mobile innovators like Apple and Google duke it out in the smartphone arena, the recent news of Amazon releasing a phone and the Firefox OS making strides in emerging markets should carry over into this segment. Additionally, startups like Pebble has been gaining traction by developing their own Pebble OS that allows them to be nimble, manageable and converse with your smartphone OS. Before a solid ad strategy can be devised, developers will be looking for a bit more cohesion and insight into what the top OS is, to maximize reach and therefore, the best return on investment. Developing across multiple OSs can be challenged on resources and capital, like the smartphone market many coupled their development strategies to follow the OS that made a big impact, and in turn, followed the money. Expect there to be more standing on the sidelines as marketers and brands have-a-wait-and-see approach to follow where OS gains are made. Engagement: Finally, the breakthrough engagement factor of wearables should also be considered. If the mouse click was the engagement factor for the desktop and touch for smartphones, will speech be the new click or swipe for the wearable category? As the technology matures, where and how interactions and engagement take place will be key drivers. Will it be a blink, a nod or a swipe? Having an idea of this will lead to an entirely new category of advertising. The best context in which to deliver ads to the consumer will also serve as a key consideration. Location & physical based context and augmented reality could really fuel this ad category. As this sector grows, other new form factors will come into play and marketers will need to cater to form and context in order to be successful. We are now on the cusp of the mainstream potential and appeal of the wearable smart device. There are still many variables that need to be played out, but the savvy marketer is planning ahead for the next opportunity. There will be plenty of failure before we find the right path, but one thing is for sure: The future is bright.

What happens when Cameras get APIs? – Why it’s important and what you need to know.

2.25 Billion Cameras will be connected to the Internet this year and developing software for them represents a unique set of challenges. Traditionally used just for security, cameras are an essential part of the Internet of Things and can provide great benefits to all sorts of software from supply chain to social media. With over 4 years experience in developing software for everything from IP Cameras to DSLRs, Marco Herbst talks through some of the largest camera installations in the world and some of the smallest and guides developers on the path to success when adding the live image to their application.

Buildings = Data: APIs and the unification of architecture, engineering, and construction


The building industry is siloed in terms of data interoperability between architects, engineers, contractors, and owners/operators – impeding their ability to analyze or leverage data produced at disparate phases of the planning, design, construction, and operation phases. The future of building data will be driven by the unification of data across the entire building lifecycle using a network of robust APIs. The implications of this unification will be drastic and will have lasting impacts on the experience of our surroundings and the ability of the internet-of-things to reach its full potential in the context of the built environment.

Learn Apache Pig (workshop)

Elephant Scale

Apache Pig is a high level data flow language for Hadoop eco system. Pig facilitates defining simple to complex workflows that can operate on data sizes ranging from gigabytes to petabytes. The simplicity of Pig scripting is big plus compared to Java Map Reduce. Pig was oringally developed at Yahoo; now Pig is heavily used by companies like Netflix, LInkedin and Yahoo.

This workshop will introduce Apache Pig to students. We will go through the Pig concepts and learn Pig Latin language. Students will learn by working on hands-on labs using Hadoop and Pig. The workshop will focus on solving practical, real world problems (no toy labs)

This is a HANDS-ON workshop.
(How to provide access to Hadoop cluster is to be determined)

Intended Audience

Health And Fitness APIs: Our Bodies, Disconnected


I could do either a solo talk on the state of fitness APIs or a panel with top executives from MyFitnessPal, RunKeeper, Under Armour/MapMyFitness, and other companies in the space.

I’d also be interested in moderating other panels or serving as an emcee or host for the event.

ReadWrite has a deep interest in the programmable world and we could lend unique editorial expertise to the event.

Intro to REST with Ajax/JSON

Hack Reactor

The goal of this highly interactive workshop is to learn the basics of interacting with a RESTful API using AJAX(with jQuery). We will discuss high level what AJAX, JSON and REST mean and then dive right into the code to see for ourselves. You will leave this workshop being able to GET data and POST data from most REST APIs. This is a highly interactive course that consists of 20 minute blocks of instruction with 20 minutes of hands-on exercises. The workshop assumes basic knowledge of JavaScript and how to use a library.