api.asciidoc

REST API

Some {kib} features are provided via a REST API, which is ideal for creating an integration with {kib}, or automating certain aspects of configuring and deploying {kib}.

Note	Access to internal {kib} API endpoints will be restricted in 9.0. Please move any integrations to publicly documented APIs.

Note	For the latest details, refer to {api-kibana}[{kib} API].

Using the APIs

Prepend any {kib} API endpoint with kbn: and send the request through Dev Tools > Console. For example:

`GET kbn:/api/index_management/indices`

Note: this will automatically prefix s/{space_id}/ on the API request if ran from a non-default Kibana Space.

Authentication

The {kib} APIs support key- and token-based authentication.

Token-based authentication

To use token-based authentication, you use the same username and password that you use to log into Elastic. In a given HTTP tool, and when available, you can select to use its 'Basic Authentication' option, which is where the username and password are stored in order to be passed as part of the call.

Key-based authentication

To use key-based authentication, you create an API key using the Elastic Console, then specify the key in the header of your API calls.

For information about API keys, refer to API keys.

API calls

API calls are stateless. Each request that you make happens in isolation from other calls and must include all of the necessary information for {kib} to fulfill the request. API requests return JSON output, which is a format that is machine-readable and works well for automation.

Calls to the API endpoints require different operations. To interact with the {kib} APIs, use the following operations:

• GET - Fetches the information.

• POST - Adds new information.

• PUT - Updates the existing information.

• PATCH - Applies partial modifications to the existing information.

• DELETE - Removes the information.

Request headers

For all APIs, you must use a request header. The {kib} APIs support the kbn-xsrf and Content-Type headers.

kbn-xsrf: true

By default, you must use kbn-xsrf for all API calls, except in the following scenarios:

• The API endpoint uses the GET or HEAD operations

• The path is allowed using the server.xsrf.allowlist setting

• XSRF protections are disabled using the server.xsrf.disableProtection setting

Content-Type: application/json

Applicable only when you send a payload in the API request. {kib} API requests and responses use JSON. Typically, if you include the kbn-xsrf header, you must also include the Content-Type header.

Request header example:

curl -X POST \
  http://localhost:5601/api/spaces/space \
  -H 'Content-Type: application/json' \
  -H 'kbn-xsrf: true' \
  -d '{
	"id": "sales",
	"name": "Sales",
	"description": "This is your Sales Space!",
	"disabledFeatures": []
}
'

{kibana-root}/docs/api/features.asciidoc {kibana-root}/docs/api/spaces-management.asciidoc {kibana-root}/docs/api/role-management.asciidoc {kibana-root}/docs/api/session-management.asciidoc {kibana-root}/docs/api/saved-objects.asciidoc {kibana-root}/docs/api/data-views.asciidoc {kibana-root}/docs/api/index-patterns.asciidoc {kibana-root}/docs/api/alerting.asciidoc {kibana-root}/docs/api/actions-and-connectors.asciidoc {kibana-root}/docs/api/cases.asciidoc {kibana-root}/docs/api/dashboard-api.asciidoc {kibana-root}/docs/api/logstash-configuration-management.asciidoc {kibana-root}/docs/api/machine-learning.asciidoc {kibana-root}/docs/api/osquery-manager.asciidoc {kibana-root}/docs/api/short-urls.asciidoc {kibana-root}/docs/api/task-manager/health.asciidoc {kibana-root}/docs/api/upgrade-assistant.asciidoc {kibana-root}/docs/api/synthetics/synthetics-api.asciidoc {kibana-root}/docs/api/uptime-api.asciidoc