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

The upstream object represents a virtual hostname and can be used to load balance incoming requests over multiple services (targets).An upstream also includes a [health checker](https://developer.konghq.com/gateway/traffic-control/health-checks-circuit-breakers/), which can enable and disable targets based on their ability or inability to serve requests.The configuration for the health checker is stored in the upstream object, and applies to all of its targets.

Kong Upstreams 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 Upstreams. 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 Upstreams 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.

Upstreams 9

The upstream object represents a virtual hostname and can be used to load balance incoming requests over multiple services (targets). An upstream also includes a [health checker](…

POST
/{workspace}/upstreams
Create a new Upstream
create-upstream 1 param body → 201401
DELETE
/{workspace}/upstreams/{UpstreamIdOrName}
Delete an Upstream
delete-upstream 3 params → 204401
GET
/{workspace}/upstreams/{UpstreamIdOrName}
Get an Upstream
get-upstream 2 params → 200401404
PUT
/{workspace}/upstreams/{UpstreamIdOrName}
Upsert a Upstream
upsert-upstream 2 params body → 200401
GET
/v2/control-planes/{controlPlaneId}/core-entities/upstreams
List all Upstreams
list-upstream 4 params → 200401
POST
/v2/control-planes/{controlPlaneId}/core-entities/upstreams
Create a new Upstream
create-upstream 1 param body → 201401
DELETE
/v2/control-planes/{controlPlaneId}/core-entities/upstreams/{UpstreamId}
Delete an Upstream
delete-upstream 3 params → 204401
GET
/v2/control-planes/{controlPlaneId}/core-entities/upstreams/{UpstreamId}
Get an Upstream
get-upstream 2 params → 200401404
PUT
/v2/control-planes/{controlPlaneId}/core-entities/upstreams/{UpstreamId}
Upsert a Upstream
upsert-upstream 2 params body → 200401

Schemas 5

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

Upstream
object
The upstream object represents a virtual hostname and can be used to loadbalance incoming requests over multiple services (targets). So for example an upstream…
23 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
Upstream_2
object
The upstream object represents a virtual hostname and can be used to loadbalance incoming requests over multiple services (targets). So for example an upstream…
23 properties 1 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

kong-upstreams-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 Upstreams 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.