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
Discovery
Learnings
Guidance
Toolbox
Alignment
API Evangelist LLC

Need help?

Contact us
Kong

Kong Routes API

Route entities define rules to match client requests. Each route is associated with a service, and a service may have multiple routes associated to it. Every request matching a given route will be proxied to the associated service. You need at least one matching rule that applies to the protocol being matched by the route.The combination of routes and services, and the separation of concerns between them, offers a powerful routing mechanism with which it is possible to define fine-grained entrypoints in Kong Gateway leading to different upstream services of your infrastructure.Depending on the protocol, one of the following attributes must be set:- `http`: At least one of `methods`, `hosts`, `headers`, or `paths`- `https`: At least one of `methods`, `hosts`, `headers`, `paths`, or `snis`- `tcp`: At least one of `sources` or `destinations`- `tls`: at least one of `sources`, `destinations`, or `snis`- `tls_passthrough`: set `snis`- `grpc`: At least one of `hosts`, `headers`, or `paths`- `grpcs`: At least one of `hosts`, `headers`, `paths`, or `snis`- `ws`: At least one of `hosts`, `headers`, or `paths`- `wss`: At least one of `hosts`, `headers`, `paths`, or `snis` A route can't have both `tls` and `tls_passthrough` protocols at same time. Learn more about the router:- [Configure routes using expressions](https://developer.konghq.com/gateway/routing/expressions/)

Documentation Provider Profile APIs.io OpenAPI GitHub

Kong Routes 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 Routes. 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 18 operations across 8 paths, and defines 9 schemas. It is described by OpenAPI 3.2.0, at version 3.14.0.

Requests are made against 5 base URLs: {protocol}://{hostname}:{port}{path}, https://global.api.konghq.com, https://us.api.konghq.com, https://eu.api.konghq.com, https://au.api.konghq.com.

18 operations 8 paths 9 schemas 4 DELETE6 GET4 POST4 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
API Key, HTTP Bearer, HTTP Bearer, HTTP Bearer, HTTP Bearer
Contact
Kong Inc
License
Apache 2.0
Resource Areas
1

Authentication & Security 5

Kong Routes API declares 5 security schemes for authenticating requests. An API key is passed in the header as Kong-Admin-Token (adminToken). 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).

  • 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 18

Across 8 paths, the API surfaces 18 operations — 4 DELETE, 6 GET, 4 POST, 4 PUT. Each is listed below with its method, path, parameters, and response codes.

Routes 18

Route entities define rules to match client requests. Each route is associated with a service, and a service may have multiple routes associated to it. Every request matching a gi…

POST
/{workspace}/routes
Create a new Route
create-route 1 param body → 201401
POST
/{workspace}/routes#RouteExpression
Create a new Route
create-route-RouteExpression 1 param body → 201401
DELETE
/{workspace}/routes/{RouteIdOrName}
Delete a Route
delete-route 3 params → 204401
GET
/{workspace}/routes/{RouteIdOrName}
Get a Route
get-route 2 params → 200401404
PUT
/{workspace}/routes/{RouteIdOrName}
Upsert a Route
upsert-route 2 params body → 200401
DELETE
/{workspace}/routes/{RouteIdOrName}#RouteExpression
Delete a Route
delete-route-RouteExpression 3 params → 204401
GET
/{workspace}/routes/{RouteIdOrName}#RouteExpression
Get a Route
get-route-RouteExpression 2 params → 200401404
PUT
/{workspace}/routes/{RouteIdOrName}#RouteExpression
Upsert a Route
upsert-route-RouteExpression 2 params body → 200401
GET
/v2/control-planes/{controlPlaneId}/core-entities/routes
List all Routes
list-route 6 params → 200401
POST
/v2/control-planes/{controlPlaneId}/core-entities/routes
Create a new Route
create-route 1 param body → 201401
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/routes/{RouteId}
Delete a Route
delete-route 3 params → 204401
GET
/v2/control-planes/{controlPlaneId}/core-entities/routes/{RouteId}
Get a Route
get-route 2 params → 200401404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/routes/{RouteId}
Upsert a Route
upsert-route 2 params body → 200401
GET
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}/routes
List all Routes associated with a Service
list-route-with-service 5 params → 200
POST
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}/routes
Create a new Route associated with a Service
create-route-with-service 2 params body → 201
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}/routes/{RouteId}
Delete a a Route associated with a Service
delete-route-with-service 3 params → 204
GET
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}/routes/{RouteId}
Get a Route associated with a Service
get-route-with-service 3 params → 200404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}/routes/{RouteId}
Upsert a Route associated with a Service
upsert-route-with-service 3 params body → 200

Schemas 9

The contract defines 9 schemas that model the data the API accepts and returns. The most detailed are RouteJson (21 properties), RouteJson_2 (21 properties), RouteExpression_2 (15 properties), RouteExpression (15 properties). Each schema is shown below with its type and property counts.

RouteExpression
object
Route entities define rules to match client requests. Each Route is associated with a Service, and a Service may have multiple Routes associated to it. Every r…
15 properties
RouteJson
object
Route entities define rules to match client requests. Each Route is associated with a Service, and a Service may have multiple Routes associated to it. Every r…
21 properties
GatewayUnauthorizedError
object
2 properties 2 required
RouteExpression_2
object
Route entities define rules to match client requests. Each Route is associated with a Service, and a Service may have multiple Routes associated to it. Every r…
15 properties
RouteJson_2
object
Route entities define rules to match client requests. Each Route is associated with a Service, and a Service may have multiple Routes associated to it. Every r…
21 properties
RouteWithoutParents
PaginationNextResponse
string
URI to the next page (may be null)
PaginationOffsetResponse
string
Offset is used to paginate through the API. Provide this value to the next list operation to fetch the next page
Route

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-routes-api-openapi.yml Raw ↑

Other APIs Kong publishes across the network.

Kong Gateway
AE Profile APIs.io
Kong AI Gateway
AE Profile APIs.io
Kong Agent Gateway
AE Profile APIs.io
Kong MCP Registry
AE Profile APIs.io
Kong Context Mesh
AE Profile APIs.io
Kong Mesh
AE Profile APIs.io
Kong Insomnia
AE Profile APIs.io
Kong ACLs API
AE Profile APIs.io
Kong Add-Ons API
AE Profile APIs.io
Kong API API
AE Profile APIs.io
Kong API Attributes API
AE Profile APIs.io
Kong API Documentation API
AE Profile APIs.io
#Routes
← Back to K APIs
API Details
ID
kong:kong-routes-api
Base URL
https://konghq.com/
Docs
https://konghq.com/products/kong-gateway
Provider
Kong
APIs.io →  GitHub →
Explore more
All APIs Providers APIs.io Network
Work with this as data

Every API here is available over the API and to AI agents over MCP. APIs is not yet its own endpoint on the v1 API. Reach this content through network search and the tag graph, or the MCP server below.

Installs https://mcp.apievangelist.com/mcp in Claude, Cursor, VS Code and the rest — one button, every client.

MCP tools for apis
4 tools reach this content
  • search_api_evangelistSearch every content type across the network at once.
  • find_relatedThe shared-tag relevance graph — what else covers this.
  • get_tagEverything one tag labels, across all content types.
  • guide_topicPRO — a curated bundle for a topic: area, guidance, rules, papers, stories, services.
All tools & prompts
Call it yourself
curl for this page
Search the network for this 
curl "https://api.apievangelist.com/v1/search?q=kong-routes-api&limit=10"
Everything under a tag 
curl "https://api.apievangelist.com/v1/tags/kong-routes-api"

Discovery needs no key. Full bodies and the synthesis endpoints are Pro.

Get an API key

Free tier, no email required. Sign in with whichever identity you already have.

GitHub Google LinkedIn

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

Where this information came from

This is an independent, third-party profile of Kong Routes 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.