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

HAProxy Discovery API

API autodiscover endpoints

HAProxy Discovery API is one of 68 APIs that HAProxy publishes on the APIs.io network, described by a machine-readable OpenAPI specification.

Tagged areas include Discovery. 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 8 operations across 8 paths, and defines 3 schemas. It is described by OpenAPI 3.2.0, at version 3.4.

Requests are made against a single base URL, /v3.

8 operations 8 paths 3 schemas 8 GET

Metadata

The identity and technical contract details declared by the specification.

Specification
OpenAPI 3.2.0
API Version
3.4
Base URL
http://{haproxy-host}:5555/v3
Authentication
HTTP Basic
Resource Areas
1

Authentication & Security 1

HAProxy Discovery API declares 1 security scheme for authenticating requests. It accepts HTTP basic authentication (basic_auth). By default, every request must be authenticated.

Paths & Operations 8

Across 8 paths, the API surfaces 8 operations — 8 GET. Each is listed below with its method, path, parameters, and response codes.

Discovery 8

API autodiscover endpoints

GET
/
Return list of root endpoints
getAPIEndpoints → 200default
GET
/services
Return list of service endpoints
getServicesEndpoints → 200default
GET
/services/haproxy
Return list of HAProxy related endpoints
getHaproxyEndpoints → 200default
GET
/services/haproxy/stats
Return list of HAProxy stats endpoints
getStatsEndpoints → 200default
GET
/services/haproxy/configuration
Return list of HAProxy advanced configuration endpoints
getConfigurationEndpoints → 200default
GET
/services/haproxy/runtime
Return list of HAProxy advanced runtime endpoints
getRuntimeEndpoints → 200default
GET
/services/haproxy/storage
Return list of HAProxy storage endpoints
getStorageEndpoints → 200default
GET
/services/haproxy/spoe
Return list of HAProxy SPOE endpoints
getSpoeEndpoints → 200default

Schemas 3

The contract defines 3 schemas that model the data the API accepts and returns. The most detailed are endpoint (3 properties), error (2 properties). Each schema is shown below with its type and property counts.

endpoints
array
Collection of endpoints
error
object
API Error
2 properties 2 required
endpoint
object
Endpoint definition
3 properties

Specification

The full machine-readable OpenAPI contract behind this narrative.

Source

haproxy-discovery-api-openapi.yml Raw ↑

Other APIs HAProxy publishes across the network.

HAProxy Runtime API
HAProxy Kubernetes Ingress Controller
HAProxy ACL API
HAProxy ACL Runtime API
HAProxy Acme API
HAProxy Acme Runtime API
HAProxy Backend API
HAProxy Backend Switching Rule API
HAProxy Bind API
HAProxy Cache API
HAProxy Configuration API
HAProxy Crt Load API
Where this information came from

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