1. The document discusses the importance of companies dogfooding or using their own APIs internally to improve API design and catch issues. 2. It recommends that development teams should only communicate with each other through API interfaces and these interfaces should be designed from the beginning to be externalizable. 3. The document also provides tips for API design such as using versioning, consistent behavior, simplicty, standards, caching and personalized onboarding to improve APIs and user experience.

1. How and Why
To Dogfood
Your API
Open path to innovation and
growth

2. “Pay close attention to the APIs -
That’s all that really matters.” - Feb
1st , 2007

3. “Faster… Launch is tomorrow”
- Feb 2nd , 2007
• “They’re using SharePoint…” (and then others)
• “This customer has 1,000 editors in 23 countries,
and 100,000 shops, each requires different editions
of the video, but all changes are to be approved by
20 people.”

4. 1. All teams expose data and functionality via
interfaces.
2. Teams must only communicate via these
interfaces.
3. There will be no other form of communication
allowed.
4. It doesn’t matter what technology is used.
5. All service interfaces, without exception, must be
designed from the ground up to be externalizable.
6. Anyone who doesn’t do this will be fired.

5. Let’s throw some big words…
1. Interoperability
2. Flexibility and Innovation
3. Cost-Efficiency
4. Automation of Processes
5. Accessible Functionality
6. Delegation of Work
7. Democratizing of Data
8. Marketplace

6. Sign up
Review with
Bus.Dev
Wait for
decision
Sign Legal
Agreements
Pay
Get API
Access
Start
Building
It’s 2014 (end of almost)…
and many APIs are still like that
=

7. Open API
Sign up
Start
Building

8. Make Your API, Your Core

9. Evolve. Never Break.
• Versioning
• Naming Conventions
• Consistent Behavior

10. Simple. Accessible.
• Standards,
don’t be afraid to break {:reinvent} them.
• Workflows,
build atomic APIs, then multirequest.
• Caching,
make it work seamlessly.
• Be mindful,
don’t assume people read, or even want to.

11. What’s Next?
• University,
personalized & structured learning, certifications.
• BPaaS,
creating workflows without writing code.
• Adaptive and proactive docs,
distributing new best practices safely & timely.
• Faster, personalized on-boarding,
your own personalized cloud consultant.

12. What you already knew…
• Be a platform. API first, then apps.
• No backdoors, be your own first customer.
• Distributed scale – design your core with APIs.
• Nobody cares – make it seamless.
• Nobody reads – make it literal.
• Remove all barriers for participation.
• Use atomic APIs, automate with multirequest.
• Use the right technology for the situation/user,
don’t be afraid to reinvent standards.

13. Zohar Babin, Sr. Director of Ecosystem, Kaltura
Zohar.Babin@Kaltura.com
@zohar
NEW YORK . SAN FRANCISCO . LONDON . TEL-AVIV . SINGAPORE . SAO PAULO