# Streams Documentation
> Backfilled and real-time blockchain data delivery. Filter blocks, transactions, traces, receipts, and logs in JavaScript, then route to Postgres, S3, Snowflake, BigQuery, or a webhook.

- [Getting Started with Streams](https://www.quicknode.com/docs/streams.md): Getting Started with Streams
- [/streams/rest/v1/streams/{id}/activate REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-activate-stream-by-id.md): Activates (resumes) a paused stream by its unique ID, causing it to begin processing and delivering blocks again.
- [/streams/rest/v1/streams/{id}/pause REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-pause-stream-by-id.md): Pauses an active stream by its unique ID, temporarily stopping it from processing and delivering new blocks. Use this endpoint when you need to perform maintenance on your destination or temporarily halt data ingestion. While paused, the stream does not consume API credits. Pausing does not delete the stream or its configuration.
- [/streams/rest/v1/streams/test_filter REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-test-filter.md): Tests a JavaScript filter function against a specific block on a given network and dataset without creating or modifying a stream. Use this endpoint to validate and debug your base64-encoded filter logic before deploying it to a live stream. You specify the network (e.g., ethereum-mainnet), dataset (e.g., block, block_with_receipts, logs), the base64-encoded filter function, and a block number to test against. The response returns the output of your filter, allowing you to verify the transformation logic, check for errors, and confirm the output shape matches your destination's expectations. This is an essential development tool for iterating on filter functions safely.
- [Azure Blob Storage Destination](https://www.quicknode.com/docs/streams/destinations/azure.md): Learn how to configure Azure Blob Storage as a destination for your Quicknode Streams to store blockchain data in the cloud.
- [Blockchain Data Backfilling](https://www.quicknode.com/docs/streams/backfilling.md): Learn how to backfill blockchain data easily based on your project's needs using Quicknode Streams.
- [DELETE /streams/rest/v1/streams REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-delete-all-streams.md): Permanently deletes all streams in your account in a single operation. This is a destructive action that cannot be undone — all streams will stop processing and delivering data immediately. Use with extreme caution, primarily for cleanup during development or testing environments. In production, prefer deleting streams individually using the Delete Stream by ID endpoint to avoid accidental data loss.
- [DELETE /streams/rest/v1/streams/{id} REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-delete-stream-by-id.md): Permanently deletes a specific stream by its unique ID. Use this endpoint to remove a stream that is no longer needed. Once deleted, the stream stops processing and delivering data, and the action cannot be undone.
- [FAQ](https://www.quicknode.com/docs/streams/faq.md): Frequently asked questions (FAQ) about Streams
- [Filters](https://www.quicknode.com/docs/streams/filters.md): Filters enable you to filter your streams payload and to customize the data that is sent to your destination.
- [GET /streams/rest/v1/streams REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-retrieve-all-streams.md): Retrieves a paginated list of all streams in your account. Use this endpoint to get an overview of your deployed streams, including their configuration, status, destination details, and current processing position. Supports limit and offset query parameters for pagination (default limit is 20). Each stream object in the response includes its ID, network, dataset, region, filter function, block range, batch size, destination configuration, status, and the last delivered block number. This is useful for building dashboards, auditing your stream configurations, or programmatically managing multiple streams.
- [GET /streams/rest/v1/streams/{id} REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-retrieve-stream-by-id.md): Retrieves the full configuration and current state of a single stream by its unique ID. Use this endpoint to inspect a specific stream's settings including its network, dataset, filter function, block range, destination attributes, reorg handling configuration, and current processing position (sequence number and current hash). This is particularly useful for monitoring a stream's progress during backfills, debugging delivery issues, or verifying configuration changes after an update.
- [GET /streams/rest/v1/streams/enabled_count REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-get-enabled-count.md): Returns the total number of currently active (enabled) streams in your account. Use this lightweight endpoint to quickly check how many streams are running without fetching full stream details. This is useful for monitoring, quota tracking, or building dashboards that display account-level stream usage at a glance.
- [How to Build and Deploy a Webhook Service for Streams](https://www.quicknode.com/docs/streams/destinations/webhooks/deploy.md): In this guide, we'll show you how to build and deploy a webhook service for receiving data from Quicknode Streams using various programming languages.
- [PATCH /streams/rest/v1/streams/{id} REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-update-stream.md): Updates the configuration of an existing stream. Use this endpoint to modify a stream's name, filter function, destination, destination attributes, extra destinations, batch size, metadata settings, reorg handling, distance-from-tip, notification email, and other configuration options without needing to delete and recreate the stream. All body parameters are optional. This is useful for changing a webhook URL, updating a filter function, switching compression settings, adjusting retry parameters, or adding extra destinations. Note that network, dataset, and region cannot be changed — create a new stream instead.
- [POST /streams/rest/v1/streams REST API Endpoint](https://www.quicknode.com/docs/streams/rest-api/streams-rest-create-stream.md): Creates a new Stream with a specified blockchain network, dataset type, destination, and optional filter function. Use this endpoint to programmatically set up real-time or historical blockchain data pipelines. You can configure the stream to start from a specific block (for backfills) or from the latest block (for real-time streaming), set batch sizes for optimized throughput, choose a destination (webhook, S3, Azure Blob Storage, or Postgres), and attach a base64-encoded JavaScript filter to transform data server-side before delivery. The stream can be created in an active or paused state. Supports reorg detection, distance-from-tip configuration, elastic batching, notification emails for stream termination alerts, and extra destinations for multi-destination delivery.
- [Reorg Handling](https://www.quicknode.com/docs/streams/reorg-handling.md): Reorg Handling
- [Setting Up Streams with PostgreSQL](https://www.quicknode.com/docs/streams/destinations/postgre-sql.md): Setting Up Streams with PostgreSQL
- [Setting Up Streams with S3-Compatible Storage](https://www.quicknode.com/docs/streams/destinations/s3.md): Setting Up Streams with S3-Compatible Storage
- [Setting Up Streams with Webhook Destination](https://www.quicknode.com/docs/streams/destinations/webhooks.md): Setting Up Streams with Webhook Destination
- [Streams Billing](https://www.quicknode.com/docs/streams/billing.md): Understand Streams API credit-based billing and estimate costs based on network, dataset type, and blocks processed.
- [Streams Data Sources](https://www.quicknode.com/docs/streams/data-sources.md): Quicknode Streams allows users to access a variety of datasets tailored for different types of blockchain data. Datasets are supported across chains and multiple destinations.
- [Streams Destinations Overview](https://www.quicknode.com/docs/streams/destinations.md): Overview
- [Streams REST API](https://www.quicknode.com/docs/streams/rest-api/getting-started.md): Introducing the Streams REST API