Originally presented at API Strat and Practice conference in Boston 2016 by me and Mandy Whaley, this presentation shows the multiple archetypes that you could encounter while trying to govern APIs at your company.

1. How To Train Your APIs
Amanda Whaley Ashley Roach

2. Intro/Preamble
• Background
• Worked in teams building apis
• Worked on api designs
• Now working in helping others DX / API design standards, and API adoption
• Restate the theme of the session
• As we thought about things, we thought there might be these 8 archetypes

3. What is an archetype
• These are kind of flexible definitions
• noun
• the original pattern or model from which all things of the same kind are copied
or on which they are based; a model or first form; prototype.
• (in Jungian psychology) a collectively inherited unconscious idea, pattern of
thought, image, etc., universally present in individual psyches.

4. Card Slides

12. How to use the cards…
• Be a citizen dragon-spotter so we can help solve these problems as a
community

13. API Unconference
Gather API-curious and API-experts in one place
Unconference format adds complexity, but mystery and fun

14. API Center of Excellence
Clearing house for best practices

15. Normalize on CSS, not format (for docs)
Continuous doc publishing system
Multi-format
Backed by git

16. API Design Guide
Useful as a point of conversation
Not used as a bludgeon

17. Onboarding process evolution
Fairly strict and manual onboarding process
Gradually opening this up as teams “get it”

18. Things that remain to be solved
• API Gateways??? One or more?
• What about non-REST?
• Support concerns/burden? ”Tale of Two APIs: Twitter & Slack” Example
SPVSS info here?