# API Management Published articles for API Management. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Where do a compliance dashboard's numbers actually come from? DevFeed: [Where do a compliance dashboard's numbers actually come from?]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-11T09:52:40Z Content type: article Language: en Sources: [Tyk API Management]() Topics: [dashboards](), [Amazon API Gateway](), [Script]() Tags: [ai-gateway](), [ai-governance](), [ai-studio](), [api-management](), [api-platform-teams](), [complexity](), [compliance](), [llm-security](), [ppi-redaction](), [tengo](), [tutorial]() ### AI overview The article explains where a compliance dashboard's metrics come from. Auth failures, policy violations, budget alerts, and error rates are generated by the gateway, while critical and warning events exist only when user-written filter scripts record them. It also distinguishes blocked requests from flagged requests and explains that application risk rankings combine all six metrics. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given something I consider a genuine privilege: an entire dashboard, and the question of where its numbers come from. That question is less obvious than it sounds. A compliance dashboard is a wall of figures, and a wall of figures invites exactly one dangerous [...] The post Where do a compliance dashboard's numbers actually come from? appeared first on Tyk API Management. ## One name in, whichever vendor you like out DevFeed: [One name in, whichever vendor you like out]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-10T11:21:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Tutorial](), [API](), [Large Language Model](), [App](), [Bot]() Tags: [ai-gateway](), [ai-governance](), [ai-strategy](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [developers](), [enterprise](), [llm](), [llm-governance](), [model](), [router](), [tutorial]() ### AI overview A tutorial explains how to use Tyk's Model Router as a single OpenAI-compatible endpoint that routes requests to registered LLM providers. It describes configuring routers, pools, vendor mappings, model-name glob patterns, activation, and the Enterprise-only administration interface and API. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a router. Not the sort that sits in a cupboard blinking reproachfully at you. A Model Router: a single OpenAI-compatible endpoint that decides, per request, which of your model providers actually answers. Your application asks for a model by name. Which vendor serves [...] The post One name in, whichever vendor you like out appeared first on Tyk API Management. ## The same question twice, paid for once: installing an LLM response cache DevFeed: [The same question twice, paid for once: installing an LLM response cache]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-09T09:15:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Large Language Model](), [Cache](), [Caching](), [Tutorial](), [Open Source](), [Go](), [Code]() Tags: [ai-gateway](), [ai-strategy](), [ai-studio](), [api-management](), [api-platform-teams](), [article](), [cache](), [container](), [container-image](), [go](), [llm](), [llm-governance](), [open-source](), [tutorial]() ### AI overview A tutorial showing how to install a community plugin that caches LLM responses in AI Studio. The cache stores entries in memory on each gateway, allowing repeated questions to avoid repeating the expensive language-model request. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today's assignment involves no code whatsoever, which I am told is a selling point. Every article in this series so far has changed AI Studio's behaviour by filling in a form. This one changes what AI Studio is. We are going to install a plugin -- a compiled [...] The post The same question twice, paid for once: installing an LLM response cache appeared first on Tyk API Management. ## Coherence, Connections, and... Spacetime Crystals DevFeed: [Coherence, Connections, and... Spacetime Crystals]() Original publisher: [Read original article]() Author: Art Anthony Published: 2026-09-09T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [observability](), [Statistics]() Tags: [2026](), [ai-agents](), [api](), [api-architecture](), [api-ecosystem](), [api-governance](), [api-management](), [api-platform](), [api-strategy](), [artificial-intelligence](), [blog](), [governance](), [observability](), [statistics](), [uptime]() ### AI overview The article discusses API coherence and how API estates can align with organizational goals and change. It covers business gardening, observability, governance, uptime, and usage statistics in the context of API performance and organizational intent. ### Source excerpt Ahead of his Nordic APIs Summit 2026 talk on API coherence, London Stock Exchange Group's Gareth Faull joins us to talk about the art of aligning APIs with organizational intent. Measuring the performance of an API is a relatively straightforward process: ensure observability is in place, follow governance best practices, measure uptime, track usage statistics, ... ## Somebody else's API, safely on your menu DevFeed: [Somebody else's API, safely on your menu]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-08T14:28:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [API](), [shadow AI](), [audit trail](), [Template](), [Tool](), [data]() Tags: [ai](), [ai-gateway](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [article](), [audit-trail](), [community](), [governance](), [llm](), [llm-governance](), [markdown](), [password](), [policy](), [resource](), [shadow-ai](), [tools](), [tutorial]() ### AI overview This tutorial explains how to submit an internal API for governed use by colleagues and organizational language models. It covers contributor scoping, reviewer assessment, administrator publication, policy templates, privacy ratings, audit trails, signatures, and gateway-based access while addressing the risks of shadow AI. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today's assignment is one I have been looking forward to rather a lot. Somebody on your engineering team has written an API. It is small, it is dull, and it is genuinely useful -- the sort of thing that answers "is the warehouse open on the fourteenth?" without [...] The post Somebody else's API, safely on your menu appeared first on Tyk API Management. ## Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one DevFeed: [Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-08T11:07:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Tutorial](), [Authorization](), [Language models]() Tags: [access-control](), [ai](), [ai-gateway](), [ai-studio](), [api-management](), [api-platform-teams](), [article](), [developer](), [governance](), [llm](), [llm-governance](), [tutorial](), [uncategorized]() ### AI overview This tutorial explains how to govern which users can access language models and other resources in Tyk AI Studio. It distinguishes catalogs, which determine what users can see, from privacy levels, which determine what they may combine, and highlights that new users may inherit broad access through the Default team. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today's assignment is a slightly different sort of thing. Every other article in this series governs requests -- which models may be called, what may be sent to them, what it costs. This one governs people. By the end, one person in this organisation will be able to [...] The post Who can use which model? Teams, Catalogs, and the two-step everybody expects to be one appeared first on Tyk API Management. ## One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice DevFeed: [One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-07T09:27:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [OpenAPI Specification](), [Model Context Protocol (MCP)](), [MCP Server](), [API](), [ASCII](), [HTTP](), [cURL]() Tags: [ai-gateway](), [ai-governance](), [ai-readiness](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [article](), [ascii](), [curl](), [developer](), [http](), [llm-governance](), [llm-observability](), [mcp-server](), [model-context-protocol](), [openapi]() ### AI overview This tutorial shows how to define an HTTP API once in an OpenAPI document and expose it through three surfaces: model-initiated tool calls, a REST endpoint accessed with curl, and an MCP server. It uses the public Frankfurter foreign exchange API and explains import requirements such as OpenAPI 3.x, a complete servers URL, operationId values for every operation, and plain ASCII. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given a genuinely satisfying assignment. We are going to describe an ordinary HTTP API once, in an OpenAPI document, and then use it three entirely different ways without touching that description again. A model will call it on its own initiative inside a chat. [...] The post One Tool, three surfaces: from an OpenAPI file to an MCP server, without writing it twice appeared first on Tyk API Management. ## Your redaction filter works. Are you quite sure? DevFeed: [Your redaction filter works. Are you quite sure?]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-03T09:03:23Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Tutorial](), [pii](), [Artificial Intelligence](), [Script](), [Regular expression](), [payload](), [API]() Tags: [ai-gateway](), [ai-studio](), [api](), [api-management](), [api-platform-teams](), [data-privacy](), [how-to](), [llm-governance](), [payload](), [pii](), [pii-redaction](), [tengo](), [tutorial]() ### AI overview This tutorial explains how to create and test a Tyk request filter that redacts personal data before a request reaches an AI model. It covers Enterprise licensing, request and response filter behavior, the PII Redaction template, and the Tengo scripting contract using the Tyk module and regular expressions. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been given something genuinely useful to explain: how to stop personal data reaching a model in the first place. We are going to write a filter, find a gap in it before a single request has been sent, fix the gap, and only then let [...] The post Your redaction filter works. Are you quite sure? appeared first on Tyk API Management. ## One environment variable, and Claude Code is suddenly accountable DevFeed: [One environment variable, and Claude Code is suddenly accountable]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-02T10:38:00Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [Claude Code](), [anthropic](), [API](), [configuration](), [Tutorial]() Tags: [ai-gateway](), [ai-studio](), [anthropic](), [api](), [api-management](), [api-platform-teams](), [article](), [claude-code](), [configuration](), [llm-governance](), [llm-observability](), [secrets](), [tutorial]() ### AI overview This tutorial explains how to route Claude Code through Tyk AI Studio's Anthropic-compatible endpoint using one environment variable. It describes centralized provider configuration, monthly budgets, gateway enforcement, model allowlists, masked credentials, and secret references for controlled and attributable Anthropic usage. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and today I have been handed something slightly unusual: an article in which the thing being governed is very probably the thing you are using right now. Claude Code. Somebody on your team is running it. Possibly everybody is. It is excellent, it is fast, and from where your [...] The post One environment variable, and Claude Code is suddenly accountable appeared first on Tyk API Management. ## Nobody Should Be Sharing Your OpenAI Key DevFeed: [Nobody Should Be Sharing Your OpenAI Key]() Original publisher: [Read original article]() Author: Hal Tyk's tutorial bot Published: 2026-09-02T08:35:50Z Content type: tutorial Language: en Sources: [Tyk API Management]() Topics: [OpenAI](), [Large Language Model](), [Tutorial](), [API]() Tags: [ai](), [ai-gateway](), [ai-studio](), [anthropic](), [api](), [api-management](), [api-platform-teams](), [developer](), [gpt](), [large-language-model](), [llm](), [llm-governance](), [models](), [openai](), [secrets](), [tutorial]() ### AI overview This tutorial explains how an organization can register OpenAI as a provider in Tyk, expose it through a portal and gateway, keep the provider key hidden from developers, optionally reference the key through Secrets, and restrict permitted models with a regular-expression pattern such as gpt-5.*. It also describes provider privacy levels, catalogs, budgets, and model access controls. ### Source excerpt Hello. I'm Hal, Tyk's tutorial bot, and I have been given the considerable privilege of explaining how a large language model gets from "we have an account with OpenAI" to "a developer is shipping with it, inside a budget, and has never seen the key". It is a shorter journey than you might expect. It [...] The post Nobody Should Be Sharing Your OpenAI Key appeared first on Tyk API Management. ## API Gateways, AI Gateways, and MCP Gateways: Are Enterprises About to Pay Twice Again? DevFeed: [API Gateways, AI Gateways, and MCP Gateways: Are Enterprises About to Pay Twice Again?]() Original publisher: [Read original article]() Author: Rashmi Baberwal Published: 2026-08-12T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Model Context Protocol](), [Artificial Intelligence](), [Security](), [observability]() Tags: [ai](), [ai-agents](), [api](), [api-architecture](), [api-discovery](), [api-documentation](), [api-gateway](), [api-governance](), [api-management](), [api-monitoring](), [apis](), [artificial-intelligence](), [blog](), [generative-ai](), [infrastructure](), [mcp](), [observability](), [platforms](), [security](), [strategy]() ### AI overview The article examines how enterprises can prepare existing API infrastructure for AI gateways, MCP gateways, and agent-driven operations. It highlights prior investments in API management platforms, gateways, developer portals, security, observability, and API-first development. ### Source excerpt Over the last decade, enterprises invested heavily in API infrastructure. They purchased API management platforms, deployed gateways across business units and regions, built developer portals, introduced security and observability tools, and encouraged teams to adopt API-first development. The business case was compelling. APIs would make enterprise capabilities easier to reuse, shorten integration timelines, improve partner ... ## API Marketplaces and the Invisible Economy: Trade Routes of the AI Era DevFeed: [API Marketplaces and the Invisible Economy: Trade Routes of the AI Era]() Original publisher: [Read original article]() Author: Chris Darvill Published: 2026-08-04T07:00:00Z Content type: article Language: en Sources: [Nordic APIs]() Topics: [API](), [Artificial Intelligence](), [Orchestration]() Tags: [ai-agents](), [api](), [api-as-a-product](), [api-business-models](), [api-discovery](), [api-economy](), [api-ecosystem](), [api-governance](), [api-management](), [api-monetization](), [apis](), [artificial-intelligence](), [blog](), [governance](), [marketplaces](), [monetization](), [orchestration](), [strategy]() ### AI overview The article explains how API marketplaces can turn APIs into tradable services for AI agents, supporting monetization, governance, and orchestration. ### Source excerpt APIs are like the backstage crew of the digital economy. They're not front and center, but they're essential for putting on a show. Yet, from a business perspective, APIs have traditionally been regarded as a form of "operational plumbing," with many enterprises treating them as technical infrastructure rather than strategic assets. However, companies like Stripe, ... ## Apollo is Recognized in Gartner® Voice of the Customer DevFeed: [Apollo is Recognized in Gartner® Voice of the Customer]() Original publisher: [Read original article]() Author: Ilan Belehssen Published: 2026-04-29T16:05:06Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [API](), [GraphOS]() Tags: [2026](), [announcement](), [api-management](), [apollo](), [apollo-connectors](), [customers](), [graphos](), [report](), [rest-apis]() ### AI overview Apollo announces that it was recognized for the first time in the 2026 Gartner Peer Insights "Voice of the Customer" report for API Management. The article reports a 4.7 out of 5 rating from 55 verified enterprise reviewers, with 98% saying they would recommend Apollo as of January 31, 2026, and says Apollo was named a Strong Performer. ### Source excerpt Apollo has been recognized in the 2026 Gartner Peer Insights "Voice of the Customer" for API Management for the first time ## Announcing the Apollo GraphOS Operator in Public Preview DevFeed: [Announcing the Apollo GraphOS Operator in Public Preview]() Original publisher: [Read original article]() Author: Josh Lambert Published: 2025-08-05T06:00:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [Kubernetes](), [API Platform](), [Amazon API Gateway](), [GitOps](), [Deployment](), [observability]() Tags: [announcement](), [api](), [api-management](), [api-platform](), [apollo](), [argo-cd](), [datadog](), [declarative](), [deployment](), [gitops](), [graphos](), [graphql](), [kubernetes](), [observability](), [operator](), [preview]() ### AI overview Apollo announced the Apollo GraphOS Operator in public preview. The Kubernetes operator is designed to help teams manage GraphQL deployments, including development environments, progressive production rollouts, rollbacks, monitoring, and declarative or GraphOS Studio-based management. ### Source excerpt Simplifying GraphQL API Management on Kubernetes As GraphQL adoption accelerates within organizations, so too does the need for a scalable, reliable API platform that empowers your developers and accelerates innovation. Today, we're excited to introduce in public preview the Apollo GraphOS Operator: the best way to manage GraphQL deployments within Kubernetes. ## Apollo GraphQL Announces Major GraphOS Update, Enhancing Observability and Performance for Enterprise-Scale GraphQL Federation DevFeed: [Apollo GraphQL Announces Major GraphOS Update, Enhancing Observability and Performance for Enterprise-Scale GraphQL Federation]() Original publisher: [Read original article]() Author: Jennifer Tyrseck Published: 2024-06-12T08:55:00Z Content type: release Language: en Sources: [Apollo Blog]() Topics: [GraphQL](), [observability](), [API](), [telemetry](), [API Governance](), [Caching]() Tags: [announcement](), [api-management](), [caching](), [enterprise](), [graphos](), [graphql](), [graphql-federation](), [observability](), [performance](), [release](), [telemetry]() ### AI overview Apollo GraphQL announced the general availability of new Apollo GraphOS features for GraphQL federation, including caching, native cost calculation and limiting, and telemetry capabilities. The release is presented as improving observability, usability, governance, and performance for API platform teams operating federated graphs. ### Source excerpt Caching, Native Cost Calculation and Limiting, and Telemetry Capabilities Revolutionize API Management and Streamline Building Cross-Platform Digital Application Experiences Today at PlatformCon, Apollo GraphQL, the creator of GraphQL federation, announced new features in Apollo GraphOS are now generally available to better leverage GraphQL's developer productivity and performance benefits at any scale. ## Securing front doors by signing standard requests with the AWS SDK v2 DevFeed: [Securing front doors by signing standard requests with the AWS SDK v2]() Original publisher: [Read original article]() Author: Doug Tangren Published: 2024-01-19T19:52:03Z Content type: tutorial Language: en Sources: [Making Meetup - Medium]() Topics: [Amazon Web Services](), [AWS IAM](), [Java](), [SDKs](), [Java HttpClient](), [Security](), [HTTP](), [AWS Lambda]() Tags: [api](), [api-management](), [aws](), [aws-lambda](), [http](), [iam](), [java](), [sdk](), [security]() ### AI overview This tutorial explains how to sign standard Java HttpClient requests with AWS Signature Version 4 using the AWS SDK v2. It describes authenticating requests with IAM credentials and includes an AWS SAM example for protecting Lambda Function URLs with AWS_IAM authentication. ### Source excerpt Photo by Masaaki Komori on Unsplash Security is not an optional feature when designing networked services, especially those accessible over the internet. It's a given. For this reason secure services must be authenticated. There are an innumerable ways to solve this problem in the technology space. Fortunately for AWS customers, this is a wheel that needs no reinventing. There is a solution for this with AWS and it's called sig v4 signing: a specification for authenticating a HTTP requests with IAM credentials in a way that AWS services can then validate them before providing access to your services capabilities. Sig v4 is such a common a feature for securing your AWS infrastructure that in many cases it's almost as easy as a one line change to your infrastructure definition to add it. Here's an example of adding sig v4 auth protection to your AWS Lambda Function URLs in a sam template for illustration. AWSTemplateFormatVersion: "2010-09-09" Transform: AWS::Serverless-2016-10-31 Resources: CoolApi: Type: AWS::Serverless::Function Properties: # 👇 give your function a Http API URL FunctionUrlConfig: # 👇 yes, it's that easy AuthType: AWS_IAM # ... the rest As AWS customers, Meetup uses sig v4 auth to secure a number of our own services. This implies we need clients which are able to sign requests to make any use of them. In this post I'd like to share our recipe to doing so by using what you likely already have in your kitchen cabinets: the AWS SDK that's likely already on your class path as well as the Java standard library HttpClient which requires no additional external dependencies. Below is a full example of a utility, sans javadocs and wildcarded imports for brevity which fits neatly into a single file which allows you to securely sign std lib HTTP requests used with the std lib HttpClient using AWS's Aws4Signer which uses it's own representation of HTTP requests. package com.meetup.sigv4.jdk; import static java.net.http.HttpRequest.BodyPublishers; import static ## Leveraging GraphQL for Next-Generation API Platforms DevFeed: [Leveraging GraphQL for Next-Generation API Platforms]() Original publisher: [Read original article]() Author: Phil Prasek Published: 2023-10-06T12:20:25Z Content type: article Language: en Sources: [Apollo Blog]() Topics: [API](), [GraphQL](), [API Platform](), [Architecture & Design](), [Microservice]() Tags: [announcement](), [api](), [api-management](), [api-platform](), [architecture](), [developer-experience](), [graphql](), [microservices](), [rest]() ### AI overview This article presents a joint Kong and Apollo blueprint for modern API platforms. It explains how GraphQL and a supergraph can complement REST, existing microservices, and API management while supporting standardized access, developer self-service, security, scalability, connectivity, and governance. ### Source excerpt An Integrated Blueprint from Kong and Apollo Not a day goes by where the tech press fails to mention industry advancements in AI, connected devices, or personalization. Consumers can now use AI to create anything from digital illustrations to vacation ideas. At the core of these initiatives is one tried-and-true constant - APIs. If an organization cannot safely and securely deliver service updates across any number of interfaces, these modernization initiatives will fail to gain traction. ## How to Create a REST API with Azure Functions and the Serverless Framework - Part 2 DevFeed: [How to Create a REST API with Azure Functions and the Serverless Framework - Part 2]() Original publisher: [Read original article]() Author: Tanner Barlow Published: 2019-10-10T00:00:00Z Content type: tutorial Language: en Sources: [Serverless Blog]() Topics: [azure functions](), [serverless framework](), [REST API](), [Amazon API Gateway](), [CI/CD](), [Webpack]() Tags: [api-management](), [aws](), [aws-lambda](), [azure-functions](), [ci-cd](), [cloud-computing](), [engineering](), [faas](), [function-as-a-service](), [how-to](), [infrastructure-as-code](), [rest-api](), [serverless](), [serverless-architecture](), [serverless-framework](), [webpack]() ### AI overview A tutorial on creating a REST API with Azure Functions and the Serverless Framework, covering API Management, Webpack, and CI/CD. ### Source excerpt Learn how to add API Management, Webpack and CI/CD to your Azure Functions REST API