2018-05-29 21:07:40 +00:00
|
|
|
---
|
|
|
|
|
layout: api
|
|
|
|
|
page_title: Connect - HTTP API
|
2020-04-07 18:55:19 +00:00
|
|
|
description: >-
|
2023-05-05 17:41:40 +00:00
|
|
|
The `/connect` endpoints provide access to service mesh-related operations for
|
2020-04-07 18:55:19 +00:00
|
|
|
intentions and the certificate authority.
|
2018-05-29 21:07:40 +00:00
|
|
|
---
|
|
|
|
|
|
|
|
|
|
# Connect HTTP Endpoint
|
|
|
|
|
|
|
|
|
|
The `/connect` endpoints provide access to
|
2023-05-05 17:41:40 +00:00
|
|
|
[service mesh-related](/consul/docs/connect) operations for
|
2018-05-29 21:07:40 +00:00
|
|
|
intentions and the certificate authority.
|
|
|
|
|
|
2023-05-05 17:41:40 +00:00
|
|
|
There are also service mesh-related endpoints in the
|
2023-01-25 16:52:43 +00:00
|
|
|
[Agent](/consul/api-docs/agent) and [Catalog](/consul/api-docs/catalog) APIs. For example,
|
2018-05-29 21:07:40 +00:00
|
|
|
the API for requesting a TLS certificate for a service is part of the agent
|
2023-05-05 17:41:40 +00:00
|
|
|
APIs. And the catalog API has an endpoint for finding all mesh-capable
|
2018-05-29 21:07:40 +00:00
|
|
|
services in the catalog.
|
|
|
|
|
|
2023-05-05 17:41:40 +00:00
|
|
|
The noun _connect_ is used throughout this documentation to refer to the connect
|
|
|
|
|
subsystem that provides Consul's service mesh capabilities.
|
|
|
|
|
Where you encounter the _noun_ connect, it is usually functionality specific to
|
|
|
|
|
service mesh.
|
|
|
|
|
|
2018-05-29 21:07:40 +00:00
|
|
|
Please choose a sub-section in the navigation for more information.
|
