[Internal]: Add curl/API tab for Kibana Streams

[octavioranieri]

Description

Add tab for curl/API under https://www.elastic.co/docs/solutions/observability/streams/wired-streams#streams-wired-streams-ship

Resources

https://www.elastic.co/docs/solutions/observability/streams/wired-streams#streams-wired-streams-ship

Which documentation set does this change impact?

Elastic On-Prem and Cloud (all)

Feature differences

Users can identify how the request should come from the API instead of relying in shippers.

What release is this request related to?

N/A

Serverless release

24 Oct 2025

Collaboration model

The documentation team

Point of contact.

Main contact: @LucaWintergerst

Stakeholders:

[flash1293]

Not sure whether that's too much, but if jq is installed we could provide a oneliner like this to ingest a file quick-n-dirty:

cat your_logs.txt | jq -Rc '{ "create" : { } }, { "message": . }' | \
curl -XPOST "http://your-elasticsearch-host:9200/logs/_bulk?filter_path=took,errors,items.*.error" \
 -H "Content-Type: application/x-ndjson" \
 -H "Authorization: ApiKey YOUR_BASE64_TOKEN_HERE" \
 --data-binary @-

There is definitely a kind of user that would like that.

[mdbirnstiehl]

Examples:

POST /logs/_bulk
{ "create": {} }
{ "@timestamp": "2025-05-05T12:12:12", "body": { "text": "Hello world!" }, "resource": { "attributes": { "host.name": "my-host-name } } }
// .. some more like that

POST /logs/_bulk
{ "create": {} }
{ "@timestamp": "2025-05-05T12:12:12", "body": { "text": "Hello world!" }, "resource": { "attributes": { "host.name": "my-host-name } } }
{ "create": {} }
{ "@timestamp": "2025-05-05T12:12:12", "message "Hello world!" , "host.name": "my-host-name }