How AI is applied across API Evangelist and APIs.io. Read my AI disclosure →
API Evangelist API Evangelist
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Kong Event Gateway Listeners API

A listener represents hostname-port or IP-port combinations that connect to TCP sockets. Listeners need at least as many ports as backend brokers if you use port mapping in a Forward to Virtual Cluster policy. For SNI routing, you can route all brokers using a listener with only one port. Ports can be expressed as a single port or range. Addresses can be IPv4, IPv6, or hostnames.A listener can have policies that enforce TLS certificates and perform SNI routing. The listener runs at Layer 4 of the network stack. In Kong Event Gateway, listeners first take in the connection and then route the TCP connection to a virtual cluster based on conditions defined in listener policies.

Kong Event Gateway Listeners API is one of 139 APIs that Kong publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

This API exposes 1 JSON Schema definition.

Tagged areas include Event Gateway Listeners. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, a JSON-LD context, a GitHub repository, an API reference, authentication docs, and 1 JSON Schema.

This API exposes 5 operations across 2 paths, and defines 23 schemas. It is described by OpenAPI 3.2.0, at version 3.14.0.

Requests are made against 4 base URLs: https://global.api.konghq.com, https://us.api.konghq.com, https://eu.api.konghq.com, https://au.api.konghq.com.

5 operations 2 paths 23 schemas 1 DELETE2 GET1 POST1 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.14.0
Base URL
https://konghq.com/
Authentication
HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Contact
License
Resource Areas
1

Authentication & Security 4

Kong Event Gateway Listeners API declares 4 security schemes for authenticating requests. It accepts HTTP bearer tokens (Token) (personalAccessToken). It accepts HTTP bearer tokens (Token) (systemAccountAccessToken). It accepts HTTP bearer tokens (JWT) (konnectAccessToken). It accepts HTTP bearer tokens (JWT) (serviceAccessToken). By default, every request must be authenticated.

  • personalAccessToken — The personal access token is meant to be used as an alternative to basic-auth when accessing Konnect via APIs. You can generate a Personal Access Token (PAT) f…
  • systemAccountAccessToken — The system account access token is meant for automations and integrations that are not directly associated with a human identity. You can generate a system acc…
  • konnectAccessToken — The Konnect access token is meant to be used by the Konnect dashboard and the decK CLI to authenticate with.
  • serviceAccessToken — The Service access token is meant to be used between internal services.

Paths & Operations 5

Across 2 paths, the API surfaces 5 operations — 1 DELETE, 2 GET, 1 POST, 1 PUT. Each is listed below with its method, path, parameters, and response codes.

Event Gateway Listeners 5

A listener represents hostname-port or IP-port combinations that connect to TCP sockets. Listeners need at least as many ports as backend brokers if you use port mapping in a Forw…

GET
/v1/event-gateways/{gatewayId}/listeners
List Event Gateway Listeners
list-event-gateway-listeners 4 params → 200401403
POST
/v1/event-gateways/{gatewayId}/listeners
Create Event Gateway Listener
create-event-gateway-listener 1 param body → 201400401403
GET
/v1/event-gateways/{gatewayId}/listeners/{eventGatewayListenerId}
Get an Event Gateway Listener
get-event-gateway-listener 2 params → 200401403404
PUT
/v1/event-gateways/{gatewayId}/listeners/{eventGatewayListenerId}
Update Event Gateway Listener
update-event-gateway-listener 2 params body → 200400401403
DELETE
/v1/event-gateways/{gatewayId}/listeners/{eventGatewayListenerId}
Delete Event Gateway Listener
delete-event-gateway-listener 2 params → 204401403404

Schemas 23

The contract defines 23 schemas that model the data the API accepts and returns. The most detailed are EventGatewayListener (8 properties), BaseError (5 properties), CursorMetaPage (5 properties), InvalidParameterChoiceItem (5 properties). Each schema is shown below with its type and property counts.

BadRequestError
BaseError
object
standard error
5 properties 4 required
InvalidParameterMinimumLength
object
5 properties 4 required
UpdatedAt
string
An ISO-8601 timestamp representation of entity update date.
CreatedAt
string
An ISO-8601 timestamp representation of entity creation date.
CursorMetaPage
object
5 properties 3 required
UnauthorizedError
NotFoundError
StringFieldContainsFilter
object
Filters on the given string field value by fuzzy match.
1 property 1 required
InvalidParameterMaximumLength
object
5 properties 4 required
InvalidParameterStandard
object
4 properties 2 required
EventGatewayListenerAddresses
array
Which address or addresses to listen on. 0.0.0.0 means all addresses on the host. :: means all addresses on the host in IPv6. If 0.0.0.0 or :: is used, there c…
InvalidParameterChoiceItem
object
5 properties 4 required
InvalidParameters
array
invalid parameters
Labels
object
Labels store metadata of an entity that can be used for filtering an entity list or for searching across entity types. Keys must be of length 1-63 characters,…
CursorMeta
object
Pagination metadata.
1 property 1 required
EventGatewayListenerPort
ForbiddenError
StringFieldEqualsFilter
object
Filters on the given string field value by exact match.
1 property
InvalidParameterDependentItem
object
5 properties 4 required
EventGatewayListener
object
Listeners are used to expose virtual clusters to clients.
8 properties 6 required
InvalidRules
string
invalid parameters rules
EventGatewayListenerPorts
array
Which port or ports to listen on. There can be multiple ways to define ports: - as a single port, e.g. 9092 - as a range of ports, e.g. 9092-9094 It's possible…

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-event-gateway-listeners-api-openapi.yml Raw ↑

Other APIs Kong publishes across the network.

Kong Gateway
Kong AI Gateway
Kong Agent Gateway
Kong MCP Registry
Kong Context Mesh
Kong Mesh
Kong Insomnia
Kong ACLs API
Kong Add-Ons API
Kong API API
Kong API Attributes API
Kong API Documentation API
Where this information came from

This is an independent, third-party profile of Kong Event Gateway Listeners API, published by API Evangelist. We do not operate, host, resell, or support these APIs, and we are not affiliated with or endorsed by the company unless stated above. Everything here is built from publicly available information — the company's own site, developer portal, documentation, public repositories, and the specifications it publishes for public use. Nothing is obtained by breaching a system, defeating an access control, or using credentials.

The Kin Score and Agent Readiness rating are independently calculated assessments of a company's public API artifacts, scored against a published rubric. They are not certifications, endorsements, security assessments, or audits.

Corrections, re-scores, and removal are free — no partnership or purchase required, and you do not need to justify the request. A removed company is recorded as unrated, never scored zero for having asked. Acknowledgement within one business day; removal within two.

info@apievangelist.com · Read the full data-sourcing policy →
On a security or compliance team? Put security in the subject line and you will get a person, not a form — we will tell you exactly which public URLs this profile was built from.