--- type: "article" title: "Weekly API Evangelist Governance (Guidance)" newsletter: "API Evangelist" newsletter_handle: "apievangelist" newsletter_url: "https://usecommune.com/n/apievangelist" author: "Kin Lane (@kinlane)" published: "2025-03-24T13:17:05.977Z" canonical_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-18" markdown_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-18.md" chat_url: "https://usecommune.com/n/apievangelist/a/weekly-api-evangelist-governance-guidance-18/chat" source_url: "https://buttondown.com/apievangelist/archive/weekly-api-evangelist-governance-guidance-copy/" body_source: "native" likes: 0 replies: 0 body_words: 514 --- # Weekly API Evangelist Governance (Guidance) *Let’s give a warm Monday welcome to our*[*documentation partner Theneo*](https://bit.ly/41n9vPS)*and our*[*SDK partner APIMATIC*](https://bit.ly/3UFE1AP)*. API Evangelist storytelling occurs because of Theneo and APIMATIC, and I am thankful to have their support for this exciting ride!* Could imagine if we could just pause any new API work for a month or two, and [just take the moment to map out and make sense of the APIs we already have and use](https://apievangelist.com/2025/03/18/do-not-do-anything-new-just-map-the-apis-you-have/). I know it’s a delusional thought in today’s insane business climate, but imagine for just a second that we could, [take the time to survey, assess, and consider what matters the most across our existing business operations](https://services.apievangelist.com/store/api-surveying-and-assessment/). [![](https://assets.buttondown.email/images/4d996c4e-a659-4d2c-813d-465d1156101e.png?w=960&fit=max)](https://apievangelist.com/2025/03/18/do-not-do-anything-new-just-map-the-apis-you-have/) *Trapped in the Sprawling Chaos of APIs* I spent the week helping my customers realize that their [OpenAPI is the same thing as the business requirements for their API](https://apievangelist.com/2025/03/17/your-openapi-is-your-api-requirements/), and I find that once you begin to see OpenAPI at this level, you will be less likely to [freely give up your API intellectual property over to cloud services](https://apievangelist.com/2025/03/17/when-you-wont-publish-api-publicly-but-freely-give-up-api-intellectual-property-over-to-cloud-services/) in this [backwards OpenAPI world we live in](https://apievangelist.com/2025/03/19/the-backwards-openapi-world-we-live-in/). It this world OpenAPI is seen as the tangible outputs of a standardized governed API lifecycle, but [OpenAPI really isn’t the thing](https://apievangelist.com/2025/03/20/openapi-is-not-the-thing/)—it really is just all about your teams working in concert. [![](https://assets.buttondown.email/images/9497e372-0d11-4a0f-a20b-496b4b2efa62.png?w=960&fit=max)](https://apievangelist.com/2025/03/20/openapi-is-not-the-thing/) *Your Diverse Teams Doing the API Planning* Building on last week’s work to evaluate the default [Spectral](https://apievangelist.com/2025/03/14/evaluating-the-default-spectral-api-governance-ruleset/) and [Vacuum](https://apievangelist.com/2025/03/14/evaluating-the-default-doctor-and-vacuum-api-governance-ruleset/) API governance rules, I profiled the default rulesets of [Redocly](https://apievangelist.com/2025/03/20/default-redocly-rules/) and [APIMATIC](https://apievangelist.com/2025/03/19/the-default-apimatic-rules/). And like OpenAPI, in the end [API governance rules are not the thing](https://apievangelist.com/2025/03/20/api-governance-rules-are-not-the-thing/)—it is the tooling and awareness teams have around the rules. This awareness will replace the [a strange silence amidst the noise of the everyone clamoring to govern the API sprawl](https://apievangelist.com/2025/03/19/the-silence-and-noise-of-apisjson-openapi-json-schema-arazzo-and-spectral-or-vacuum-rules/) that has emerged in the average enterprise organization. [![](https://assets.buttondown.email/images/b3c60c3b-8af3-4f9d-bf7d-4d018b1aad28.png?w=960&fit=max)](https://www.youtube.com/watch?v=h_hrbamY3nY&list=PL5x2w5x0IRnHzljjSmPApbhBHgp3NeTdM&index=2&ab_channel=KinLane%2CTheAPIEvangelist) *Weekly API Governance Conversation* If you want to make more sense of what I am talking about when it comes API governance I recommend our weekly API governance conversation at 12:00 PM EST. [This weeks conversation focused how API governance](https://www.youtube.com/watch?v=h_hrbamY3nY&list=PL5x2w5x0IRnHzljjSmPApbhBHgp3NeTdM&index=2&ab_channel=KinLane%2CTheAPIEvangelist) provides [a secure baseline for companies to begin working](https://apievangelist.com/2025/03/21/api-governance-rules-provide-a-secure-baseline-to-start-from/), looks at [what a valid OpenAPI is](https://apievangelist.com/2025/03/21/what-is-a-valid-openapi/), as well [managing your OpenAPI source of truth](https://apievangelist.com/2025/03/21/an-openapi-driven-pipeline-workflow-from-yesterdays-api-governance-weekly/), and [what observability means to API governance](https://apievangelist.com/2025/03/21/the-venn-diagram-of-api-governance-and-api-observability/). [![](https://assets.buttondown.email/images/d8e6fded-349d-4bc2-8f94-693d5c2c5882.png?w=960&fit=max)](https://apievangelist.com/2025/03/21/the-venn-diagram-of-api-governance-and-api-observability/) *API Governance & Observability* The weekly API governance conversation has been very successful, which is something that has pushed me to pivot a bit on [the weekly API knowledge builders on schema, APIs, rules, operations, changes, and evangelism](https://apievangelist.com/#knowledge). I have been charging hourly for these sessions, but will be opening the time slots up publicly for free, while making the original curriculum available via a 12 week email newsletter. Ultimately I don’t want to be charging enterprise teams for the knowledge I provide, and I will continue exploring how I can convince API service providers to help fund this work that I am injecting into enterprise operations. *If you need API Evangelist to help out with API governance*[*please let us know how we can help*](https://apievangelist.com/contact/)*. And thank you again to*[*APIMATIC*](https://bit.ly/3NyONos)*and*[*Theneo*](https://bit.ly/41n9vPS)*for their continued support. If you are interested in sponsoring our work and site please*[*review out sponsorship package*](https://partners.apievangelist.com/)*, and drop me an*[*email today*](mailto:info@apievangelist.com)*.* *** ## Discussion No replies yet.