It is time to say goodbye: This version of Elastic Cloud Enterprise has reached end-of-life (EOL) and is no longer supported.
The documentation for this version is no longer being maintained. If you are running this version, we strongly advise you to upgrade. For the latest information, see the current release documentation.
Proxy HTTP PUT request
editProxy HTTP PUT request
editProxies the HTTP PUT request to the cluster. You must specify the X-Management-Request
HTTP header. NOTE: Use this endpoint for management purposes. It does not provide high performance.
Request
editPUT /api/v1/clusters/kibana/{cluster_id}/proxy/{kibana_path}
Path parameters
editName | Type | Required | Description |
---|---|---|---|
|
|
Y |
The Kibana deployment identifier |
|
|
Y |
The URL part to proxy to the Kibana cluster. Example: /api/spaces/space or /api/upgrade_assistant/status |
Headers
editName | Type | Required | Description |
---|---|---|---|
|
|
Y |
When set to |
Request body
edit(string
) The JSON payload that is used to proxy the Kibana deployment.
Responses
edit-
200
-
The request has been processed successfully through the proxy
-
404
-
(
BasicFailedReply
) The cluster specified by {cluster_id} cannot be found (code: 'clusters.cluster_not_found')
To perform this operation, you must be authenticated by means of one of the following methods: apiKey, basicAuth.
Request example
editcurl -XPUT {{hostname}}/api/v1/clusters/kibana/{cluster_id}/proxy/{kibana_path} \ -H "Authorization: ApiKey $ECE_API_KEY" \ -H X-Management-Request: string