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

Envoy Text Completions API

Legacy text completions endpoints compatible with the OpenAI completions API.

Envoy Text Completions API is one of 15 APIs that Envoy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Text Completions. The published artifact set on APIs.io includes an OpenAPI specification, API documentation, an API reference, a getting-started guide, a GitHub repository, and a changelog.

This API exposes 1 operation across 1 path, and defines 4 schemas. It is described by OpenAPI 3.2.0, at version 0.2.0.

Requests are made against a single base URL, https://{gateway-host}.

1 operations 1 paths 4 schemas 1 POST

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
0.2.0
Server
https://{gateway-host}
Authentication
HTTP Bearer
Terms of Service
Resource Areas
1

Authentication & Security 1

Envoy Text Completions API declares 1 security scheme for authenticating requests. It accepts HTTP bearer tokens (bearerAuth). By default, every request must be authenticated.

  • bearerAuth — Bearer token authentication. The token is configured per route in the AIGatewayRoute Kubernetes custom resource. For AI provider backends, the gateway may auto…

Paths & Operations 1

Across 1 path, the API surfaces 1 operation — 1 POST. Each is listed below with its method, path, parameters, and response codes.

Text Completions 1

Legacy text completions endpoints compatible with the OpenAI completions API.

POST
/v1/completions
Envoy Create a text completion
createCompletion body → 200400401429

Schemas 4

The contract defines 4 schemas that model the data the API accepts and returns. The most detailed are Completion (6 properties), CompletionRequest (5 properties), UsageInfo (3 properties), ErrorResponse (1 property). Each schema is shown below with its type and property counts.

UsageInfo
object
Token usage statistics for the API request
3 properties
ErrorResponse
object
Error response returned when an API request fails
1 property
Completion
object
A completed text completion response from the AI model
6 properties
CompletionRequest
object
Request body for the legacy text completions endpoint
5 properties 2 required

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

envoy-text-completions-api-openapi.yml Raw ↑

Other APIs Envoy publishes across the network.

Envoy xDS APIs
Envoy API V3
Envoy Gateway API
Envoy Certificates API
Envoy Chat API
Envoy Clusters API
Envoy Configuration API
Envoy Health API
Envoy Listeners API
Envoy Logging API
Envoy Models API
Envoy Runtime API
Where this information came from

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