List streams
List the `kafka`/`nats` Data Sources attached to a project (both running and stopped streams are included — this is a DS-attachment listing, not a running-task listing).
List the kafka/nats Data Sources attached to a project (both running
and stopped streams are included — this is a DS-attachment listing, not a
running-task listing).
Authorization
SymetryMLAuth HMAC-SHA256 signature-based authentication: requests are signed with
your secret key and sent with the Customer-ID, Sym-date,
Authorization, Content-MD5 and sym-version headers.
See SymetryML REST API Security
for the signature algorithm and a complete example.
In: header
Path Parameters
User/Customer identifier
Project identifier
Response Body
application/json
application/json
curl -X GET "https://example.com/c1/projects/nbra_prj_iris/streams/list"{ "statusCode": 200, "statusString": "OK", "values": { "stringList": { "values": [ "nats_stream_0:nats", "nats_stream_1:nats" ] } }}{ "statusCode": 500, "statusString": "Generic Exception [java.lang.NullPointerException: Cannot invoke \"com.rtlm.core.projects.SymetryProject.getId()\" because \"p\" is null]", "values": {}}Stop stream GET
Suspend the background consumer task for a running `kafka`/`nats` Data Source without detaching/deleting it — the Data Source remains attached to the project and can be resumed with [Start stream](/docs/api-reference/streams/projects-project-streams-dsname-start-get).
Browse stream sources POST
List the topics/streams available on a Kafka or NATS JetStream server, without creating a Data Source. Distinct from `POST /{user}/projects/dsbrowse`, which browses file-based data sources (S3, SFTP, etc.) — this endpoint only understands `kafka` and `nats` in `values.type`. * **Kafka**: always returns a flat list of topics in `values.files`, each formatted as `<topic name>:<partition count>`. Topics starting with `_` (internal Kafka topics) are excluded. `values.path` is ignored. * **NATS**: if `values.path` is empty/omitted, returns the JetStream **stream** names in `values.dirs`. If `values.path` is set to a stream name, returns the **subjects** within that stream in `values.files`, echoing the stream name back in `values.path`. An unknown NATS stream name is **not** an error: the response is a `200` whose `dsdirectoryListing` carries only `ok: true`, with neither `dirs` nor `files`. `ok` defaults to `true` and is present on every response; unset list/path fields are omitted from the JSON entirely.