AuthThe Elastic Stack includes Elastic's core products such as Elasticsearch, Kibana, Logstash, and Beats.AvailabilityPlannedWe plan to add this functionality in a future Elastic Stack update. Subject to changes.Unless stated otherwise on the page, this functionality is available when your Elastic Stack is deployed on Elastic Cloud Hosted, Elastic Cloud Enterprise, Elastic Cloud on Kubernetes, and self-managed environments.This documentation corresponds to the latest patch available for each minor version. If you're not using the latest patch, check the release notes for changes.
Public ingress for Kibana connector-scoped inbound events. Authenticate with an ingest token (Authorization: Bearer, or token query parameter as fallback). A successful emit returns 202. An emit that includes an HTTP ack returns that status, usually 200 with an empty body, and still emits. A connector HTTP-only ack returns 200 (JSON or a plain-text body; .inboundWebhook handshake is { challenge }) and does not emit.
Connector HTTP 200 ack. A handshake such as .inboundWebhook{ challenge } does not emit. An ack included with an emit may have an empty body, and the events are still emitted. The body may be JSON or plain-text.