- Enterprise Search Guide: other versions:
- Overview
- Getting started
- Web crawler
- Connectors
- Engines and content sources
- Programming language clients
- Search UI
- App Search and Workplace Search
- Enterprise Search server
- Run using Docker images
- Run using downloads (packages)
- Troubleshooting
- Monitoring
- Read-only mode
- Management APIs
- Monitoring APIs
- Read-only mode API
- Configuration
- Configuring encryption keys
- Configuring a mail service
- Configuring SSL/TLS
- Upgrading and migrating
- Upgrading self-managed deployments
- Upgrading from Enterprise Search 7.x
- Upgrading from Enterprise Search 7.11 and earlier
- Migrating from App Search on Elastic Cloud
- Migrating from App Search on Swiftype.com
- Migrating from self-managed App Search
- Logs and logging
- Release notes
- 8.4.3 release notes
- 8.4.2 release notes
- 8.4.1 release notes
- 8.4.0 release notes
- 8.3.3 release notes
- 8.3.2 release notes
- 8.3.1 release notes
- 8.3.0 release notes
- 8.2.3 release notes
- 8.2.2 release notes
- 8.2.1 release notes
- 8.2.0 release notes
- 8.1.3 release notes
- 8.1.2 release notes
- 8.1.1 release notes
- 8.1.0 release notes
- 8.0.1 release notes
- 8.0.0 release notes
- 8.0.0-rc2 release notes
- 8.0.0-rc1 release notes
- 8.0.0-beta1 release notes
- 8.0.0-alpha2 release notes
- 8.0.0-alpha1 release notes
Endpoints reference
editEndpoints reference
editKibana base URL
editFor each Elastic deployment, the Kibana base URL is the portion of the Kibana URL that precedes the path.
It includes the scheme, domain name, and port.
This is abbreviated to <KIBANA_BASE_URL>
throughout the docs.
For an Elastic Cloud deployment, navigate to Elastic Cloud → Deployments → deployment. Next to Kibana, Choose Copy endpoint to copy the Kibana base URL to your clipboard. For example, on Cloud a Kibana base URL might look like this:
https://my-deployment.kb.europe-west1.gcp.cloud.es.io:9243
On a self-managed deployment, find the kibana.external_url
setting in your Enterprise Search configuration settings.
For example, a self-managed Kibana base URL might look like this:
https://localhost:5601
Alternatively, open Kibana in your browser. Remove the path from the URL. The remaining portion of the URL is the base URL.
Enterprise Search base URL
editFor each Elastic deployment, the Enterprise Search base URL is the portion of the Enterprise Search URL that precedes the path.
It includes the scheme, domain name, and port.
This is abbreviated to <ENTERPRISE_SEARCH_BASE_URL>
throughout the docs.
For an Elastic Cloud deployment, navigate to Elastic Cloud → Deployments → deployment. Next to Enterprise Search, Choose Copy endpoint to copy the Enterprise Search base URL to your clipboard.
For example, on Cloud, an Enterprise Search base URL might look like this:
https://my-enterprise-search-deployment.ent.europe-west1.gcp.cloud.es.io
On a self-managed deployment, find the ent_search.external_url
setting in your Enterprise Search configuration settings.
For example, a self-managed Enterprise Search base URL might look like this:
http://localhost:3002
Workplace Search OAuth redirect URL
editIn Workplace Search, when configuring a connector, it’s often necessary to specify an OAuth redirect URL.
This is also known as a redirect URI, redirect URL, callback URI, or callback URL. The process for finding this value is the same.
Construct the redirect URL using the Kibana base URL and the following path:
<KIBANA_BASE_URL>/app/enterprise_search/workplace_search/sources/added
If you are using Kibana from a non-default space in a self-managed deployment, ensure the following:
-
Make sure your
kibana.external_url
in yourenterprise-search.yml
configuration includes the space prefix in the URL - Make sure you are using Workplace Search from that non-default space
See Spaces for more information on Kibana Spaces.