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 Keys API

A key object holds a representation of asymmetric keys in various formats. When Kong Gateway or a Kong plugin requires a specific public or private key to perform certain operations, it can use this entity.

Kong Keys 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 Keys. 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 14 operations across 6 paths, and defines 6 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.

14 operations 6 paths 6 schemas 3 DELETE5 GET3 POST3 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
License
Resource Areas
1

Authentication & Security 5

Kong Keys 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 14

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

Keys 14

A key object holds a representation of asymmetric keys in various formats. When Kong Gateway or a Kong plugin requires a specific public or private key to perform certain operatio…

POST
/{workspace}/keys
Create a new Key
create-key 1 param body → 201401
DELETE
/{workspace}/keys/{KeyIdOrName}
Delete a Key
delete-key 3 params → 204401
GET
/{workspace}/keys/{KeyIdOrName}
Get a Key
get-key 2 params → 200401404
PUT
/{workspace}/keys/{KeyIdOrName}
Upsert a Key
upsert-key 2 params body → 200401
GET
/v2/control-planes/{controlPlaneId}/core-entities/key-sets/{KeySetId}/keys
List all Keys associated with a KeySet
list-key-with-key-set 5 params → 200
POST
/v2/control-planes/{controlPlaneId}/core-entities/key-sets/{KeySetId}/keys
Create a new Key associated with a KeySet
create-key-with-key-set 2 params body → 201
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/key-sets/{KeySetId}/keys/{KeyId}
Delete a a Key associated with a KeySet
delete-key-with-key-set 3 params → 204
GET
/v2/control-planes/{controlPlaneId}/core-entities/key-sets/{KeySetId}/keys/{KeyId}
Get a Key associated with a KeySet
get-key-with-key-set 3 params → 200404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/key-sets/{KeySetId}/keys/{KeyId}
Upsert a Key associated with a KeySet
upsert-key-with-key-set 3 params body → 200
GET
/v2/control-planes/{controlPlaneId}/core-entities/keys
List all Keys
list-key 4 params → 200401
POST
/v2/control-planes/{controlPlaneId}/core-entities/keys
Create a new Key
create-key 1 param body → 201401
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/keys/{KeyId}
Delete a Key
delete-key 3 params → 204401
GET
/v2/control-planes/{controlPlaneId}/core-entities/keys/{KeyId}
Get a Key
get-key 2 params → 200401404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/keys/{KeyId}
Upsert a Key
upsert-key 2 params body → 200401

Schemas 6

The contract defines 6 schemas that model the data the API accepts and returns. The most detailed are KeyWithoutParents (10 properties), Key_2 (10 properties), Key (10 properties), GatewayUnauthorizedError (2 properties). Each schema is shown below with its type and property counts.

Key
object
A Key object holds a representation of asymmetric keys in various formats. When Kong or a Kong plugin requires a specific public or private key to perform cert…
10 properties 1 required
GatewayUnauthorizedError
object
2 properties 2 required
Key_2
object
A Key object holds a representation of asymmetric keys in various formats. When Kong or a Kong plugin requires a specific public or private key to perform cert…
10 properties 1 required
PaginationNextResponse
string
URI to the next page (may be null)
KeyWithoutParents
object
A Key object holds a representation of asymmetric keys in various formats. When Kong or a Kong plugin requires a specific public or private key to perform cert…
10 properties 1 required
PaginationOffsetResponse
string
Offset is used to paginate through the API. Provide this value to the next list operation to fetch the next page

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-keys-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 Keys 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.