USING APIS FOR INTEGRATIONS

Michael Stephanblome, Co-Founder & CEO of Bondable
Session: Business Models
API Strategy & Practice Conference, Amsterdam 2014

Transcript

1. Michael Stephanblome Co-Founder & CEO USING APIS FOR INTEGRATIONS
2. When we started to integrate APIs we thought the process would be like this…
3. When we started RESTful
4. When it turns out that it’s more like this…
5. OAUTH // OAUTH2 // OPENID // TOKEN // HANDSHAKE // CUSTOM AUTH // SHARED KEY // REST // THRIFT // SOAP // JSON // FREEFLOW TEXT // PARSER // SOAP // XML OVERHEAD // RATE LIMITATIONS // ERROR HANDLING // WEBHOOK // AUTOSAVE // STATELESS RECORDS // FILE ENCODING // IMAP APIS // STATIC IPS // API KEY CHANGES // VERSIONING // TIMEOUTS //
6. WHAT TOOK YOU SO LONG? 15% Handling Authentications 50% Exposing resources: 5% Dealing with protocols 60% Handling Data formats 20% Rate Limitations 15% Error handling 15% Integrating API into Application 20% Testing
7. API On-boarding time 1 day 2 days 3 days 4 days 5 days 6 days 7 days
8. MOST COMMON ROADBLOCKS 1. Non-standard Authentications 2. Uncommon API responses 3. Clumsy, old protocols 4. Poor documentation 5. Difficult testing environment 6. Rate limitations
9. ARE WE ANY BETTER? EASY TO USE CLOSE TO OUR USP WITH EXAMPLES TEST AND EXPAND
11. Example YOUR APP
13. michael@bondable.com @mstephanblome Contact