---
type: "article"
title: "Weekly API Governance (Guidance)"
newsletter: "API Evangelist"
newsletter_handle: "apievangelist"
newsletter_url: "https://usecommune.com/n/apievangelist"
author: "Kin Lane (@kinlane)"
published: "2024-10-07T14:00:00.000Z"
canonical_url: "https://usecommune.com/n/apievangelist/a/weekly-api-governance-guidance-9"
markdown_url: "https://usecommune.com/n/apievangelist/a/weekly-api-governance-guidance-9.md"
chat_url: "https://usecommune.com/n/apievangelist/a/weekly-api-governance-guidance-9/chat"
source_url: "https://buttondown.com/apievangelist/archive/weekly-api-governance-guidance-1198/"
body_source: "native"
likes: 0
replies: 0
body_words: 748
---

# Weekly API Governance (Guidance)

*My name is Kin Lane—I am that API Evangelist guy who has been paying attention to the technology, business, policies, and people of APIs since 2010.*

I really enjoy how this API newsletter is guiding my API work each week. It gives me enough freedom to respond in the moment to what matters each week, while also forcing me to apply myself in each area of my work and deliver something useful and practical to my audience and customers. This week I also learned that I can revisit work from previous weeks and months, recycling, but also be building upon the hard work I’ve accomplished prior to launching version 2.0 of my API Evangelist newsletter.

**Stories**

This week I am focused on talking with mainstream companies about their API operations and tailoring my storytelling to what they need, [learning to speak more about integrations and business outcomes](https://apievangelist.com/2024/10/06/i-just-want-my-data-content-and-algorithms-in-the-services-my-customers-use/), rather just API blah blah blah, as I [help enterprises think through how they can get their data, content, and algorithms into other platforms and services](https://apievangelist.com/2024/10/06/developing-your-api-integration-strategy/).

![](https://assets.buttondown.email/images/973cd50b-d3b5-485f-a302-d367736ec6ec.png?w=960&fit=max)

**Conversations**

I spoke withwith[Jamie Tanna, Engineering Productivity at Elastic](https://conversations.apievangelist.com/sessions/2024-09-19-jamie-tanna-elastic.html) about the realities of API versioning and management change, as well as [Robert Buchanan, API Evangelist Driving API Integrations and API First practices at Procter & Gamble](https://conversations.apievangelist.com/sessions/2024-09-18-robert-buchanan-pg.html) about where the deficiencies are in our API operations.

![](https://assets.buttondown.email/images/6585d4ff-d944-45ee-8f2e-60f0ec1c052b.jpg?w=960&fit=max)

*API Evangelist Conversations*

I really enjoy learning from people like Jamie about versioning because it is one of the hardest aspects of doing APIs, and I’ll kvetch with Robert about the realities of doing APIs anytime, because he sees things like I do, is way smarter than I am, and isn’t afraid to tell it like it is.

**Guidance**

I am putting a lot of work into my API guidance right now, ensuring that it covers all of the policies and rules I apply during API reviews. My approach to API governance centers around [API guidance being self-service](https://guidance.apievangelist.com/guidance/self-service.html), but also [just-in-time](https://guidance.apievangelist.com/guidance/just-in-time.html). Meaning guidance should be available as text and videos 24/7 in easily accessible location, and it should always be linked up as part of API governance enforcement during design, develop, and build-time.

![](https://assets.buttondown.email/images/5d750994-8167-491b-8a88-d80e058172e7.png?w=960&fit=max)

*Linting Rules Applied at Design-Time*

Every one of [my rules you will encounter during an API review](https://api-evangelist-tools.github.io/apis-io-search-api-api-validator/) comes with a link back to the relative API guidance with text and video guidance, as well as examples of how to accomplish what is being governed.

**Services**

I am here to [help you plan and execute the governance of your enterprise API operations](https://apievangelist.com/services/) across the key areas areas of your operations thats teams will need help.

**Strategy, Platform, Policies, Rules, Lifecycle, Guidance, and Evangelism**

[Strategic API services](https://apievangelist.com/services/) are designed to work in concert with more tactical API services, helping you invest at variable rates when it comes to your API strategy.

**Discovery**

I have profiled [300+ of the Amazon Web Service APIs](https://cloud.apis.io/apis/amazon-web-services/apis/) and continuing to profile Azure, Google, and the [other cloud service providers](https://cloud.apis.io/apis/). You can find all of the [APIs.json](https://github.com/api-search/search-api) and [OpenAPI](https://openapis.org/) artifacts for these APIs on GitHub, which are used to power the [APIs.io search engine](https://apis.io/).

![](https://assets.buttondown.email/images/234b3b9f-13de-40c8-a14a-ee223aafa2cf.png?w=960&fit=max)

*[APIs.io](http://APIs.io) Cloud Search Node*

**The API Commons**

The API Commons interface license provides a legal position of the naming, ordering, and overall design of your API, not just the code or other parts. An interface license will help define the legal tone you take with how your API paths are able to be put to work within other applications and integrations when published as part of your APIs.json contract. You can find [JSON and YAMl examples of the interface license on the API Commons](https://apicommons.org/common/interface-license/), and you can [fork the GitHub repository](https://github.com/api-commons/interface-license) to apply as part of your API operations.

![](https://assets.buttondown.email/images/53c5bea2-bcd4-4713-bea6-b1f3f69d6143.png?w=960&fit=max)

*API Commons Interface License V2.0*

**A Rough Week**

I apologize for a somewhat anemic newsletter this week. I did write some of the content referenced here this week, but I also reused other pieces from previous weeks before my newsletter launched.

I am struggling to pull it together because my mother Barbara Lee Gorrell passed away on Wednesday night at the age of 74. I am devastated, and working to make sense of things.

I do not want to lose the momentum I have built up, but I am also struggling to keep going. I will be taking it easy this week, but honestly my work helps me get up off the couch. Thank you for your support, tuning in, and helping make all of this possible.

![](https://assets.buttondown.email/images/bdec7f95-4fed-4daa-940d-d4887fa585ce.jpeg?w=960&fit=max)

*Me, My Little Sister Angela, and Mother Barbara*

[![](https://assets.buttondown.email/images/efc6837c-9972-477c-a9e6-c686df089032.png?w=960&fit=max)](https://bit.ly/47QycFN)

***

## Discussion

No replies yet.
