Kong · Schema

Plugin

A Plugin entity represents a plugin configuration that will be executed during the HTTP request/response lifecycle. Plugins provide extra functionality such as authentication, rate limiting, and transformations.

API GatewayAI GatewayAI ConnectivityAgent GatewayEvent GatewayMCP RegistryService MeshLLMKafkaKonnectOpen-Source

Properties

Name Type Description
id string The unique identifier of the Plugin.
name string The name of the plugin (e.g., rate-limiting, key-auth, cors).
instance_name string An optional custom name to identify an instance of the plugin.
config object The configuration properties for the Plugin which vary depending on the plugin being configured.
protocols array A list of the request protocols that will trigger this plugin.
enabled boolean Whether the plugin is applied.
tags array An optional set of strings for grouping and filtering.
ordering object Describes a dependency to another plugin to determine plugin ordering during the access phase (Enterprise only).
service object If set, the plugin will only activate when receiving requests via the specified Service.
route object If set, the plugin will only activate when receiving requests via the specified Route.
consumer object If set, the plugin will activate only for requests where the specified Consumer has been authenticated.
consumer_group object If set, the plugin will activate only for requests within the specified Consumer Group.
created_at integer Unix epoch timestamp of when the entity was created.
updated_at integer Unix epoch timestamp of when the entity was last updated.
View JSON Schema on GitHub

JSON Schema

kong-gateway-admin-plugin-schema.json Raw ↑
{
  "$schema": "https://json-schema.org/draft/2020-12/schema",
  "title": "Plugin",
  "type": "object",
  "description": "A Plugin entity represents a plugin configuration that will be executed during the HTTP request/response lifecycle. Plugins provide extra functionality such as authentication, rate limiting, and transformations.",
  "properties": {
    "id": {
      "type": "string",
      "description": "The unique identifier of the Plugin."
    },
    "name": {
      "type": "string",
      "description": "The name of the plugin (e.g., rate-limiting, key-auth, cors)."
    },
    "instance_name": {
      "type": "string",
      "description": "An optional custom name to identify an instance of the plugin."
    },
    "config": {
      "type": "object",
      "description": "The configuration properties for the Plugin which vary depending on the plugin being configured."
    },
    "protocols": {
      "type": "array",
      "description": "A list of the request protocols that will trigger this plugin."
    },
    "enabled": {
      "type": "boolean",
      "description": "Whether the plugin is applied."
    },
    "tags": {
      "type": "array",
      "description": "An optional set of strings for grouping and filtering."
    },
    "ordering": {
      "type": "object",
      "description": "Describes a dependency to another plugin to determine plugin ordering during the access phase (Enterprise only)."
    },
    "service": {
      "type": "object",
      "description": "If set, the plugin will only activate when receiving requests via the specified Service."
    },
    "route": {
      "type": "object",
      "description": "If set, the plugin will only activate when receiving requests via the specified Route."
    },
    "consumer": {
      "type": "object",
      "description": "If set, the plugin will activate only for requests where the specified Consumer has been authenticated."
    },
    "consumer_group": {
      "type": "object",
      "description": "If set, the plugin will activate only for requests within the specified Consumer Group."
    },
    "created_at": {
      "type": "integer",
      "description": "Unix epoch timestamp of when the entity was created."
    },
    "updated_at": {
      "type": "integer",
      "description": "Unix epoch timestamp of when the entity was last updated."
    }
  }
}

Work with this as data

Every JSON Schema here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for schemas

4 MCP tools reach this
  • find_json_schemasBrowse and filter every JSON Schema in the catalog.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This JSON Schema
curl "https://apis.io/api/v1/json-schemas/kong-gateway-admin-plugin"
All schemas
curl "https://apis.io/api/v1/json-schemas?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

A second provider on the same verified email joins the account you already have.