The document discusses the business impact of private, partner, and public APIs. Private APIs have little to no business impact as they are internal and for custom or self-serve use only. Partner APIs can have a high business impact by enabling easy integrations with trusted partners and potentially becoming public APIs. Public APIs have the highest potential business impact but may only realize medium impact in reality, as they are open to everyone and have automatic business relationships but their usage is hard to predict. The document advises mixing API types as appropriate and communicating well when transitioning APIs to be more open.

1. PRESENTED BY ANDREAS KROHN
Business Impact
of Private, Partner & Public APIs

2. Technology should
serve the business

3. Where is the ROI?

4. 0%
25%
50%
75%
100%
Private Partner Public
Number of APIs ROI Number of APIs ROI Number of APIs ROI
Warning: Extremely unscientific content used just to make a point

5. 0%
25%
50%
75%
100%
Private Partner Public
Number of APIs ROI Number of APIs ROI Number of APIs ROI
Warning: Extremely unscientific content used just to make a point
probably not true

6. 0%
25%
50%
75%
100%
Private Partner Public
Number of APIs ROI Number of APIs ROI Number of APIs ROI
Warning: Extremely unscientific content used just to make a point

7. 0%
25%
50%
75%
100%
Private Partner Public
Number of APIs ROI Number of APIs ROI Number of APIs ROI
Warning: Extremely unscientific content used just to make a point
probably closer to the truth

8. definition
Private APIs
‣Internal to an org.
‣Known trusted users
‣No business relationships

9. definition
custom
Private APIs
‣1 API - 1 client
‣Specific tech. solution
‣Business impact: None

10. definition
custom
self-serve
Private APIs
‣Designed from outside in
‣Internal resource portal
‣SOA is action
‣Impact: Medium - High

11. definition
Partner APIs
‣Used by trusted partners
‣Few, known users
‣Manual business
relationships

12. definition
integration
Partner APIs
‣Easy, fast integrations
‣New opportunities
‣Impact: High

13. definition
integration
good start
Partner APIs
‣Starting point for public
APIs
‣Collect feedback

14. definition
integration
good start
internal use
Partner APIs
‣Also use internally
‣Self-service

15. definition
!
!
!
Public APIs
‣Open to everyone
‣(as long as they pay)
‣Automatic business
relationships

16. definition
for everyone
!
!
!
Public APIs
‣You don’t know how the
API will be used
‣Usage rates are critical
‣Impact: Very high?

17. definition
for everyone
for partners
!
!
!
Public APIs
‣Users can be partners
‣Manual business
relationships

18. definition
for everyone
for partners
internal use
!
!
Public APIs
‣Use public APIs internally
‣If you don’t something is
very very very wrong

19. Business
relationship
Fullfillment
Potential
Business Impact
Realistic
Business Impact
Private
(custom)
Manual
(internal)
Manual None None
Private
(self-serve)
Automatic
(internal)
Automatic
High
(for big companies)
Medium
Partner Manual Automatic High High
Public Automatic Automatic Very high Medium

20. more public
!
!
!
How to change an API
‣Designed from outside in
‣Licenses, pricing,
security, documentation…

21. more public
more private
!
!
How to change an API
‣Potential backlash
‣Communicate in time
‣Turn key users into
trusted partners

22. Mix & match as
appropriate

23. Thank you!
mashup.se
@andreaskrohn
andreas@dopter.se