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

OpenShift Routes API

Manage application routes that expose services at a hostname. Routes provide external access to services via HTTP/HTTPS, with support for TLS termination strategies including edge, passthrough, and re-encrypt.

OpenShift Routes API is one of 31 APIs that OpenShift publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Routes. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, authentication docs, pricing, a support channel, and rate-limit docs.

This API exposes 9 operations across 4 paths, and defines 13 schemas. It is described by OpenAPI 3.1.0, at version 4.17.0.

Requests are made against a single base URL, https://api.openshift.com.

9 operations 4 paths 13 schemas 1 DELETE4 GET1 PATCH1 POST2 PUT

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.1.0
API Version
4.17.0
Base URL
https://api.openshift.com
Authentication
HTTP Bearer
License
Terms of Service
Resource Areas
1

Authentication & Security 1

OpenShift Routes API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (JWT) (BearerToken). By default, every request must be authenticated.

  • BearerToken — OAuth bearer token obtained from the OpenShift OAuth server. Use 'oc whoami -t' to retrieve a token, or configure an OAuth client for programmatic access.

Paths & Operations 9

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

Routes 9

Manage application routes that expose services at a hostname. Routes provide external access to services via HTTP/HTTPS, with support for TLS termination strategies including edge…

GET
/apis/route.openshift.io/v1/routes
Openshift List Routes Across All Namespaces
listRouteForAllNamespaces 8 params → 200401
GET
/apis/route.openshift.io/v1/namespaces/{namespace}/routes
Openshift List Routes in a Namespace
listNamespacedRoute 9 params → 200401
POST
/apis/route.openshift.io/v1/namespaces/{namespace}/routes
Openshift Create a Route
createNamespacedRoute 4 params body → 200201202401
GET
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}
Openshift Read a Route
readNamespacedRoute 3 params → 200401
PUT
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}
Openshift Replace a Route
replaceNamespacedRoute 5 params body → 200201401
PATCH
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}
Openshift Patch a Route
patchNamespacedRoute 5 params body → 200401
DELETE
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}
Openshift Delete a Route
deleteNamespacedRoute 6 params → 200202401
GET
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}/status
Openshift Read Status of a Route
readNamespacedRouteStatus 3 params → 200401
PUT
/apis/route.openshift.io/v1/namespaces/{namespace}/routes/{name}/status
Openshift Replace Status of a Route
replaceNamespacedRouteStatus 5 params body → 200201401

Schemas 13

The contract defines 13 schemas that model the data the API accepts and returns. The most detailed are ObjectMeta (11 properties), RouteSpec (8 properties), Status (7 properties), OwnerReference (6 properties). Each schema is shown below with its type and property counts.

RouteTargetReference
object
Specifies the target that traffic is routed to. Weight controls the proportion of traffic sent to this backend.
3 properties 2 required
Route
object
A Route exposes a service at a hostname, enabling external access to applications in the cluster. Routes support TLS termination strategies including edge, pas…
5 properties 1 required
TLSConfig
object
TLS configuration for the route. Determines how TLS connections are handled at the router.
6 properties
RouteSpec
object
Desired state of the Route resource.
8 properties 1 required
OwnerReference
object
Contains information to identify an owning object.
6 properties 4 required
Status
object
Status is a return value for calls that do not return other objects.
7 properties
RoutePort
object
Route port configuration that specifies which service port the route points to.
1 property 1 required
RouteIngressCondition
object
Describes the state of a route at a point in time.
5 properties
ListMeta
object
Metadata for list responses including pagination tokens.
4 properties
RouteList
object
A list of Route objects.
4 properties 1 required
RouteStatus
object
Current state of the Route.
1 property
RouteIngress
object
Holds information about the places where a route is exposed.
4 properties
ObjectMeta
object
Standard Kubernetes object metadata. Every resource includes metadata such as name, namespace, labels, and annotations.
11 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

openshift-routes-api-openapi.yml Raw ↑

Other APIs OpenShift publishes across the network.

OpenShift OAuth API
OpenShift Build API
OpenShift Image API
OpenShift Project API
OpenShift Workloads API
OpenShift Network API
OpenShift Storage API
OpenShift Authorization API
OpenShift Autoscale API
OpenShift Config API
OpenShift Console API
OpenShift Cluster API
Where this information came from

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