---
published: true
layout: post
title: A More Desired Technical State of API Operations
tags:
  - Enterprise Persona
  - Technical
  - Operations
image: >-
  https://kinlane-productions2.s3.amazonaws.com/algorotoscope-master/stalin-time-japanese-carrying-over-bridge.jpeg
---
The enterprise leadership API Evangelist has been talking to is not asking a lot, they are just looking for some quick ways they can achieve, or at least get closer to a more desired technical state of API operations, giving teams the autonomy and accountability they need, while still steering the ship in the right direction.

  - We Have a Centralized Gateway
  - We Provide Centralized Resources
  - Also Support Federated Gateways
  - We Use More Standards in APIs
  - All APIs Are Observable and Traceable
  - All New APIs Are Being Governed

Everything listed here must be delivered alongside everything else already happening within the enterprise, providing an operational “overlay” for APIs to be rolled out without disrupting existing operations, forcing teams to take on additional work, and will require a centralized, but embedded team to deliver on.

<div class="alert alert-danger" role="alert" style="text-align: center;">
This is part of ongoing series to aggregate all of the conversations we've had with enterprises about their APIs over the last five years into a single outline. If you have questions or would like to contribute to the downloadable API governance products we are developing, please <a href="https://apievangelist.com/contact">reach out</a>, and you can read the <a href="https://www.linkedin.com/pulse/who-api-evangelist-speaks-being-change-agent-within-enterprise-lane-lmuse">full post on LinkedIn</a>.
</div>