Provider Data Streams

A data stream is one collection of records exposed by a Provider Plugin, such as Linear issues, GitHub pull requests, or Slack channels. The historical protocol name for a data stream is a tap. The Provider Plugin owns how each stream is fetched: transport, pagination, incremental behavior, extraction, traversal, and rate limits. A Workspace controls whether the stream is enabled and any supported connection-level overlay.

List streams

curl "https://api.parable.work/api/tenant-connector-taps/tenant-connector-taps" \
  -H "Authorization: Bearer $PARABLE_API_TOKEN"

Filter by the Provider connection identifier when working with one connection. The result combines the plugin’s stream definition with the Workspace’s current state.

Enable, update, or disable a stream

Action	Operation
Create a Workspace stream configuration	`POST /api/tenant-connector-taps/create-tenant-connector-tap`
Read one stream configuration	`GET /api/tenant-connector-taps/{id}`
Update its enabled state or supported overlay	`PATCH /api/tenant-connector-taps/{id}`
Remove the Workspace configuration	`DELETE /api/tenant-connector-taps/{id}`

Enabling a stream makes it eligible for synchronization; data does not appear until the connection successfully runs that stream. Inspect the SQL catalog before assuming a table has rows. To understand the resulting table names and columns, see the Provider Pool. To define transport, pagination, traversal, or schema behavior for a custom plugin, use the Provider Plugin authoring guides.

​List streams

​Enable, update, or disable a stream

List streams

Enable, update, or disable a stream