Skip to main content



APIStrat 2017 CFP Guide

To help encourage the open collaboration, discussions, and debates necessary to help APIStrat be successful, we invite developers, industry thought leaders, and technical experts to submit a proposal to speak.


Dates to Remember

  • CFP Open: Thursday, April 13, 2017
  • CFP Close: Friday, June 16, 2017, 11:59 PST
  • CFP Notifications: Monday, July 24, 2017
  • Schedule Announced: Week of July 31, 2017
  • Event Dates: October 31-November 2, 2017

Note: If you are unable to view Google Forms, please contact Lara Taback at


We Like First-Time Submitters!

We want to make APIStrat the best place to get to know the API community and to share your ideas and work. Chief architects and long-time industry pundits are also welcome, but if you haven't presented at APIStrat or other conferences before, we'd especially like to hear from you! If you're unsure about your proposal, please reach out to us and we will be more than happy to work with you to ensure a great fit.

APIStrat is a working conference intended for professional networking and collaboration in the API community and we work closely with our attendees, sponsors and speakers to help keep the event professional, welcoming, and friendly. If you have any questions about participating please don’t hesitate to contact us at


Code of Conduct

All speakers are required to review, and adhere to, our Code of Conduct.

Submit a Proposal

Proposal Guidelines

Consider the following as you write your proposal:

1. What is the audience going to walk away from knowing?

2. Why should YOU be the one to give this talk? You have a unique story. Tell it.

3. Be prepared to explain how this fits into the Open API Ecosystem.

There have been sessions covering a wide range of topics supporting users and contributors of Open API, and we encourage you to "think outside the box" to come up with your own unique topics.

A great talk weaves a story -- it can address issues that developers struggle with, break down and explain complicated topics, and cover new ground in technology. All breakout presentations will be 20 minutes. We are framework agnostic. We also accept panel proposals. You can indicate your format in the CFP submission.

If you choose to submit multiple talks, please do so with the understanding that they should all represent your current passions and interests. These should be as separate of talk topics as you can muster. Multiple talks do not necessarily increase your chance of being selected.

Submit a Proposal


How to Submit Your Proposal


We have done our best to make the submission process as simple as possible. Here is what you will need to prepare:


1. Choose a submission type (Breakout Session*, Panel^^, Workshop).

30-minute presentations will be limited to one primary speaker and one co-speaker. 

^^ If you are proposing a panel discussion, please make sure that you list all of your potential panelists (4 maximum) in your abstract. We will request full biographies for each if a panel is accepted.

Note: New for 2017: All panels are required to have at least one female speaker.


2. Provide a biography, including your previous speaking experience (900 characters maximum).


3. Who is your target audience? (Web Developer, New Developers, Enterprise, DevOps).


4. Provide us with an abstract about what you will be presenting at the event (900 characters maximum)


5. Describe who the audience is and what you expect them to gain from your presentation (900 characters maximum)


6. Tell us how the content of your presentation will help better Open API and open source ecosystem. (900 characters maximum)


7. Select the experience level (Beginner, Intermediate, Advanced, Any)


8. List any technical requirements that you have for your presentation over and above the standard projector, screen and wireless Internet.


Submit a Proposal


Sample Submissions


Your abstract will be the cornerstone of your proposal. 

This is your chance to *sell* your talk to the program committee, so do your best to highlight the problem/contribution/work that you are addressing in your presentation. The technical details are still important, but the relevance of what you are presenting will help the program committee during the selection process.

This is the abstract that will be posted on the website schedule, so please ensure that it is in complete sentences (and not just bullet points) and that it is written in the third person (use your name instead of “I”).

Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): How can our code be faster? What does faster means? In this journey we would walk through different performance optimization techniques you can apply to your code. We will see start from --v8-options, and we will discover how to leverage what v8 tells us to optimize our code. We will discuss hidden classes, function optimizations and deoptimizations, and inlining. We will discuss the tools and the libraries you can use to do perf analysis on your code. In this journey, we will discover that the main villain is Lord GC, and we will fight him to reclaim our memory! At the very end, we would reach a point where even allocating a callback is too slow: Ludicrous Speed.


Describe who the audience is and what you expect them to gain from your presentation.

Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): The audience is a backend developer looking for ways to improve the overall performance of their code. This talk will highlight all the different optimization techniques to make their code run faster.


Tell us how the content of your presentation will help better the Open API ecosystem.

*Note: We realize that this can be a difficult question to answer, but as with the abstract, the relevance of your presentation is just as important as the content.

Example: Reaching Ludicrous Speed ([Speaker Name], [Speaker Company]): These techniques can be applied to any code. Moreover, most OSS libraries might gain huge benefits from even a small bit of performance optimization.


Submit a Proposal


Speaker Passes

Only (1) one Primary Speaker permitted for a 90-minute Workshop and 30-minute Breakout Sessions. Primary speaker will receive a complimentary conference pass. Additional speakers will be accommodate upon request and approved by the program committee. Moderators for panel sessions will receive a complimentary passes, maximum (4) panelists and (1) moderator.

If you require travel support, we will be collect requests once sessions are accepted.

All speakers are required to review, and adhere to, our Code of Conduct.


Submit a Proposal



Community Sponsor

Media Partners