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

Service entities are abstractions of your microservice interfaces or formal APIs. For example, a service could be a data transformation microservice or a billing API.The main attribute of a service is the destination URL for proxying traffic. This URL can be set as a single string or by specifying its protocol, host, port and path individually.Services are associated to routes, and a single service can have many routes associated with it. Routes are entrypoints in Kong Gateway which define rules to match client requests. Once a route is matched, Kong Gateway proxies the request to its associated service. See the [Route documentation](https://developer.konghq.com/gateway/entities/route/) for a detailed explanation of how Kong proxies traffic.Services can be both [tagged and filtered by tags](https://developer.konghq.com/admin-api/).

Kong Services 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 Services. 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 9 operations across 4 paths, and defines 5 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.

9 operations 4 paths 5 schemas 2 DELETE3 GET2 POST2 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 Services 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 9

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

Services 9

Service entities are abstractions of your microservice interfaces or formal APIs. For example, a service could be a data transformation microservice or a billing API. The main att…

POST
/{workspace}/services
Create a new Service
create-service 1 param body → 201401
DELETE
/{workspace}/services/{ServiceIdOrName}
Delete a Service
delete-service 3 params → 204401
GET
/{workspace}/services/{ServiceIdOrName}
Get a Service
get-service 2 params → 200401404
PUT
/{workspace}/services/{ServiceIdOrName}
Upsert a Service
upsert-service 2 params body → 200401
GET
/v2/control-planes/{controlPlaneId}/core-entities/services
List all Services
list-service 6 params → 200401
POST
/v2/control-planes/{controlPlaneId}/core-entities/services
Create a new Service
create-service 1 param body → 201401
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}
Delete a Service
delete-service 3 params → 204401
GET
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}
Get a Service
get-service 2 params → 200401404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/services/{ServiceId}
Upsert a Service
upsert-service 2 params body → 200401

Schemas 5

The contract defines 5 schemas that model the data the API accepts and returns. The most detailed are Service_2 (20 properties), Service (20 properties), GatewayUnauthorizedError (2 properties). Each schema is shown below with its type and property counts.

Service
object
Service entities, as the name implies, are abstractions of each of your own upstream services. Examples of Services would be a data transformation microservice…
20 properties 1 required
GatewayUnauthorizedError
object
2 properties 2 required
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
Service_2
object
Service entities, as the name implies, are abstractions of each of your own upstream services. Examples of Services would be a data transformation microservice…
20 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-services-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 Services 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.