3 Matching Annotations
- Feb 2014
API Management Using Github
I have documented eleven approaches to using Github for API management to date:
- Design and Code
- Software development kits (SDK)
- Code Samples (Gists)
- Developer Authentication
- Developer Profiling
- Presentations and Guides
- Issue Management
- Terms of Service, Privacy, and Branding
API Services During my monitoring of the API space, I came across a new API monitoring service called AutoDevBot, which monitors all your API endpoints, and notifies you when something goes wrong. Pretty standard feature in a new wave of API integration tools and services I’m seeing emerge, but what is interesting is they use Github as a central place to store the settings for the API monitoring service. AutoDevBot has you clone their settings template, make changes you need to monitor your APIs, register and fire up AutoDevBot to monitor. Seems like a pretty simple way for API service providers to engage with API providers, allowing them to manage all the configuration for API services alongside their own internal API operations.
Github As The Central Presence, Definition, Configuration, And Source Code For Your API Posted on 02-05-2014 It is easy to think of Github as a central repository for your open source code—most developers understand that. I have written before about the many ways to use Github as part of your API management strategy, but in the last few months I'm really seeing Github playing more of a central role in the overall lifecycle of an API.