Consul Connect

Consul Connect Configuration Entries

Consul Connect configuration entries (service-defaults, service-resolver, service-router, service-splitter, service-intentions, mesh, proxy-defaults) that declaratively configure mesh behavior. Configuration entries are managed via the /v1/config API and via Kubernetes Custom Resource Definitions when running on Kubernetes.

GitHub

Documentation

📖
Documentation
https://developer.hashicorp.com/consul/docs/connect/config-entries

Other Resources

🔗
Reference
https://developer.hashicorp.com/consul/docs/connect/config-entries/service-defaults
🔗
Reference
https://developer.hashicorp.com/consul/docs/connect/config-entries/service-router
🔗
Reference
https://developer.hashicorp.com/consul/docs/connect/config-entries/service-splitter
🔗
APIsJSON
https://raw.githubusercontent.com/api-evangelist/consul-connect/refs/heads/main/apis.yml

Work with this as data

Every API here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
  • resolveTurn a domain, URL or GitHub org into the provider it belongs to.
  • find_cohortsEvery scored population of providers in the catalog.
All 92 tools →

Call it yourself

curl for this page
This API 
curl "https://apis.io/api/v1/apis/consul-connect-config-entries"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.

API entry from apis.yml

apis.yml Raw ↑ 
aid: consul-connect:consul-connect-config-entries
name: Consul Connect Configuration Entries
description: Consul Connect configuration entries (service-defaults, service-resolver, service-router,
  service-splitter, service-intentions, mesh, proxy-defaults) that declaratively configure mesh behavior.
  Configuration entries are managed via the /v1/config API and via Kubernetes Custom Resource Definitions
  when running on Kubernetes.
humanURL: https://developer.hashicorp.com/consul/docs/connect/config-entries
baseURL: https://developer.hashicorp.com
tags:
- Configuration Entries
- CRD
- Kubernetes
- L7 Routing
properties:
- type: Documentation
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-defaults
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-router
- type: Reference
  url: https://developer.hashicorp.com/consul/docs/connect/config-entries/service-splitter
x-features:
- service-defaults to set protocol and timeouts
- service-router for L7 path/header/method routing
- service-splitter for canary and blue/green rollouts
- service-resolver for failover and subsets
- mesh-wide configuration via the mesh entry
- Kubernetes CRDs for declarative mesh management
x-useCases:
- Implementing canary deployments via service-splitter
- Routing traffic by header for tenant isolation
- Centralizing TLS and protocol defaults