New

The executive guide to generative AI

Read more
About usPartnersSupport|Login
IMPORTANT: No additional bug fixes or documentation updates will be released for this version. For the latest information, see the current release documentation.
« Resolve copy saved objects to space conflicts API Kibana role management APIs »
Elastic Docs ›Kibana Guide [8.0] ›REST API ›Kibana spaces APIs

Disable legacy URL aliases API

edit
IMPORTANT: This documentation is no longer updated. Refer to Elastic's version policy and the latest documentation.

Disable legacy URL aliases API

edit

[preview] This functionality is in technical preview and may be changed or removed in a future release. Elastic will work to fix any issues, but features in technical preview are not subject to the support SLA of official GA features. Disable a legacy URL alias in Kibana.

Request

edit

POST <kibana host>:<port>/api/spaces/_disable_legacy_url_aliases

Request body

edit
aliases

(Required, object array) The aliases to disable.

Properties of aliases
targetSpace
(Required, string) The space where the alias target object exists.
targetType
(Required, string) The type of the alias target object.
sourceId
(Required, string) The ID of the alias source object. This is the "legacy" object ID.

Response codes

edit
204
Indicates a successful call.

Examples

edit
$ curl -X POST api/spaces/_disable_legacy_url_aliases
{
  "aliases": [
    {
      "targetSpace": "bills-space",
      "targetType": "dashboard",
      "sourceId": "123"
    }
  ]
}
Copy as curl 

This example leaves the alias intact, but the legacy URL for this alias, http://localhost:5601/s/bills-space/app/dashboards#/view/123, will no longer function. The dashboard still exists, and you can access it with the new URL.

« Resolve copy saved objects to space conflicts API Kibana role management APIs »

On this page

Was this helpful?
Feedback