reorganize sidebar: isolate candlestick + data streams api for clarity

Author: dev-dist

src/config/sidebar.ts

@@ -434,47 +434,53 @@ export const SIDEBAR: Partial<Record<Sections, SectionEntry[]>> = {
           url: "data-streams/reference/overview",
         },
         {
-          title: "Data Streams REST API",
-          url: "data-streams/reference/interface-api",
-        },
-        {
-          title: "Candlestick REST API",
-          url: "data-streams/reference/candlestick-api",
-        },
-        {
-          title: "WebSocket",
-          url: "data-streams/reference/interface-ws",
-        },
-        {
-          title: "Authentication",
-          url: "data-streams/reference/authentication",
+          title: "Data Streams API",
+          url: "data-streams/reference/data-streams-api",
           children: [
             {
-              title: "JavaScript examples",
-              url: "data-streams/reference/authentication/javascript-examples",
+              title: "Authentication",
+              url: "data-streams/reference/data-streams-api/authentication",
+              children: [
+                {
+                  title: "JavaScript examples",
+                  url: "data-streams/reference/data-streams-api/authentication/javascript-examples",
+                },
+                {
+                  title: "TypeScript examples",
+                  url: "data-streams/reference/data-streams-api/authentication/typescript-examples",
+                },
+                {
+                  title: "Go examples",
+                  url: "data-streams/reference/data-streams-api/authentication/go-examples",
+                },
+                {
+                  title: "Rust examples",
+                  url: "data-streams/reference/data-streams-api/authentication/rust-examples",
+                },
+              ],
+            },
+            {
+              title: "API Reference",
+              url: "data-streams/reference/data-streams-api/interface-api",
             },
             {
-              title: "TypeScript examples",
-              url: "data-streams/reference/authentication/typescript-examples",
+              title: "WebSocket Reference",
+              url: "data-streams/reference/data-streams-api/interface-ws",
             },
             {
-              title: "Go examples",
-              url: "data-streams/reference/authentication/go-examples",
+              title: "SDK References",
+              url: "data-streams/reference/data-streams-api/go-sdk",
+              highlightAsCurrent: ["data-streams/reference/data-streams-api/rust-sdk"],
             },
             {
-              title: "Rust examples",
-              url: "data-streams/reference/authentication/rust-examples",
+              title: "Onchain report verification (EVM chains)",
+              url: "data-streams/reference/data-streams-api/onchain-verification",
             },
           ],
         },
         {
-          title: "SDK References",
-          url: "data-streams/reference/go-sdk",
-          highlightAsCurrent: ["data-streams/reference/rust-sdk"],
-        },
-        {
-          title: "Onchain report verification (EVM chains)",
-          url: "data-streams/reference/onchain-verification",
+          title: "Candlestick API",
+          url: "data-streams/reference/candlestick-api",
         },
       ],
     },

src/content/data-streams/architecture.mdx

@@ -122,7 +122,7 @@ Read the [Getting Started](/data-streams/getting-started) guide to learn how to
 
 Active-active is a system configuration strategy where redundant systems remain active simultaneously to serve requests. Incoming requests are distributed across all active resources and load-balanced to provide high availability, scalability, and fault tolerance. This strategy is the opposite of active-passive where a secondary system remains inactive until the primary system fails.
 
-The Data Streams API services use an active-active setup as a highly available and resilient architecture across multiple distributed and fully isolated origins. This setup ensures that the services are operational even if one origin fails, which provides robust fault tolerance and high availability. This configuration applies to both the [REST API](/data-streams/reference/interface-api) and the [WebSocket API](/data-streams/reference/interface-ws). A global load balancer seamlessly manages the system to provide automated and transparent failovers. For advanced use cases, the service publishes available origins using HTTP headers, which enables you to interact directly with specific origin locations if necessary.
+The Data Streams API services use an active-active setup as a highly available and resilient architecture across multiple distributed and fully isolated origins. This setup ensures that the services are operational even if one origin fails, which provides robust fault tolerance and high availability. This configuration applies to both the [REST API](/data-streams/reference/data-streams-api/interface-api) and the [WebSocket API](/data-streams/reference/data-streams-api/interface-ws). A global load balancer seamlessly manages the system to provide automated and transparent failovers. For advanced use cases, the service publishes available origins using HTTP headers, which enables you to interact directly with specific origin locations if necessary.
 
 ### Active-Active Setup
 

src/content/data-streams/developer-responsibilities.mdx

@@ -84,8 +84,8 @@ Developers implementing Chainlink Data Streams are solely responsible for instit
 - **Code dependencies and imports:** Developers are responsible for ensuring the quality, reliability, and security of any dependencies or imported packages that they use with Chainlink Data Streams, and review and audit these dependencies and packages.
 - **Implementing Contingency Logic:** In extreme circumstances, including situations beyond the control of Chainlink node operators, Chainlink Data Streams may experience periods of unavailability or performance degradation. When a WebSocket connection is dropped, user systems must manage reconnections effectively. Developers are responsible for creating contingency plans tailored to their specific application needs, such as:
   - Implementing the [Data Streams Architecture](/data-streams/architecture),
-  - Adopting an [active-active](/data-streams/architecture#active-active-multi-site-deployment) deployment strategy and [configuring the SDK](/data-streams/reference/go-sdk#config-struct) to support multiple concurrent WebSocket connections,
-  - Retrieving any potentially missing reports via the [REST API](/data-streams/reference/interface-api).
+  - Adopting an [active-active](/data-streams/architecture#active-active-multi-site-deployment) deployment strategy and [configuring the SDK](/data-streams/reference/data-streams-api/go-sdk#config-struct) to support multiple concurrent WebSocket connections,
+  - Retrieving any potentially missing reports via the [REST API](/data-streams/reference/data-streams-api/interface-api).
 
 ### Additional Considerations on Data Usage and Verification
 

src/content/data-streams/index.mdx

@@ -77,9 +77,9 @@ You can access Chainlink Data Streams through SDKs and APIs, allowing you to bui
 
 Access data directly through REST APIs or WebSocket connections using our SDKs:
 
-- **[Go SDK](/data-streams/reference/go-sdk)** - Full-featured SDK with comprehensive examples
-- **[Rust SDK](/data-streams/reference/rust-sdk)** - High-performance SDK for Rust applications
-- **[REST API](/data-streams/reference/interface-api)** or **[WebSocket](/data-streams/reference/interface-ws)** - Direct access to Data Streams endpoints
+- **[Go SDK](/data-streams/reference/data-streams-api/go-sdk)** - Full-featured SDK with comprehensive examples
+- **[Rust SDK](/data-streams/reference/data-streams-api/rust-sdk)** - High-performance SDK for Rust applications
+- **[REST API](/data-streams/reference/data-streams-api/interface-api)** or **[WebSocket](/data-streams/reference/data-streams-api/interface-ws)** - Direct access to Data Streams endpoints
 
 ### Getting started
 
@@ -89,7 +89,7 @@ Access data directly through REST APIs or WebSocket connections using our SDKs:
 
 1. Try the API: Follow our [hands-on tutorial](/data-streams/tutorials/api-go) to fetch and decode your first report.
 
-1. Implement Verification: Add [onchain verification](/data-streams/reference/onchain-verification) to ensure data authenticity in your smart contracts.
+1. Implement Verification: Add [onchain verification](/data-streams/reference/data-streams-api/onchain-verification) to ensure data authenticity in your smart contracts.
 
 ### Streams Trade: An alternative implementation
 

…ta-streams/reference/candlestick-api.mdx …eams/reference/candlestick-api/index.mdxsrc/content/data-streams/reference/candlestick-api.mdx renamed to src/content/data-streams/reference/candlestick-api/index.mdx src/content/data-streams/reference/candlestick-api.mdx renamed to src/content/data-streams/reference/candlestick-api/index.mdx

@@ -12,7 +12,7 @@ import DataStreams from "@features/data-streams/common/DataStreams.astro"
 
 <DataStreams section="dsNotes" />
 
-The Candlestick API is designed and implemented to satisfy the [TradingView implementation spec](https://www.tradingview.com/broker-api-docs/rest-api-spec/#tag/Data-Integration), the industry standard for sharing open-high-low-close (OHLC) aggregated trading data.
+The Candlestick API is designed and implemented to satisfy [TradingView data integration specifications](https://www.tradingview.com/broker-api-docs/rest-api-spec/#tag/Data-Integration), the industry standard for sharing open-high-low-close (OHLC) aggregated trading data.
 
 Alignment with the TradingView spec allows for TradingView integration and direct customer access to prices without resorting to consuming and decoding reports for non-transactional use cases, like dashboards, analytics platforms, portfolio trackers, research tools, and more.
 

…reference/authentication/go-examples.mdx …reams-api/authentication/go-examples.mdxsrc/content/data-streams/reference/authentication/go-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/go-examples.mdx src/content/data-streams/reference/authentication/go-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/go-examples.mdx

@@ -15,9 +15,9 @@ import DataStreams from "@features/data-streams/common/DataStreams.astro"
 
 Below are complete examples for authenticating with the Data Streams API in Go. Each example shows how to properly generate the required headers and make a request.
 
-To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/authentication) page.
+To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/data-streams-api/authentication) page.
 
-**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/go-sdk) or [Rust SDK](/data-streams/reference/rust-sdk), you don't need to implement the authentication logic manually.
+**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) or [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk), you don't need to implement the authentication logic manually.
 
 ## API Authentication Example
 
@@ -223,7 +223,7 @@ While this example demonstrates the authentication mechanism, production applica
 - **Error types**: Define custom error types for better error handling
 - **Testing**: Add unit tests for HMAC generation and integration tests
 
-For production use, consider using the [Go SDK](/data-streams/reference/go-sdk) which handles authentication automatically and provides built-in fault tolerance.
+For production use, consider using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) which handles authentication automatically and provides built-in fault tolerance.
 
 ## WebSocket Authentication Example
 
@@ -508,4 +508,4 @@ While this example already includes many production-ready features (keepalive, t
 - **Health checks**: Expose WebSocket connection status for monitoring systems
 - **Testing**: Add unit tests for HMAC generation and mock WebSocket server for integration tests
 
-For production use, consider using the [Go SDK](/data-streams/reference/go-sdk) which handles authentication automatically and provides built-in fault tolerance for streaming connections.
+For production use, consider using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) which handles authentication automatically and provides built-in fault tolerance for streaming connections.

…reams/reference/authentication/index.mdx …ata-streams-api/authentication/index.mdxsrc/content/data-streams/reference/authentication/index.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/index.mdx src/content/data-streams/reference/authentication/index.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/index.mdx

@@ -8,10 +8,10 @@ metadata:
   keywords: ["Authentication", "HMAC", "API Key", "API Secret", "Signature", "Security", "Data Streams"]
 whatsnext:
   {
-    "Learn about the REST API Interface": "/data-streams/reference/interface-api",
-    "Learn about the WebSocket Interface": "/data-streams/reference/interface-ws",
-    "Explore the Go SDK": "/data-streams/reference/go-sdk",
-    "Explore the Rust SDK": "/data-streams/reference/rust-sdk",
+    "Learn about the REST API Interface": "/data-streams/reference/data-streams-api/interface-api",
+    "Learn about the WebSocket Interface": "/data-streams/reference/data-streams-api/interface-ws",
+    "Explore the Go SDK": "/data-streams/reference/data-streams-api/go-sdk",
+    "Explore the Rust SDK": "/data-streams/reference/data-streams-api/rust-sdk",
   }
 isIndex: true
 ---
@@ -26,8 +26,9 @@ This page explains how to authenticate with the Chainlink Data Streams API, cove
 
 <Aside type="note" title="Data Streams SDKs">
   The Data Streams SDKs handle authentication automatically. If you're using the [Go
-  SDK](/data-streams/reference/go-sdk) or [Rust SDK](/data-streams/reference/rust-sdk), you don't need to implement the
-  authentication logic manually.
+  SDK](/data-streams/reference/data-streams-api/go-sdk) or [Rust
+  SDK](/data-streams/reference/data-streams-api/rust-sdk), you don't need to implement the authentication logic
+  manually.
 </Aside>
 
 ## Authentication Requirements
@@ -114,10 +115,10 @@ Even for GET requests and WebSocket connections, you need to include a body hash
 
 Below are complete examples for authenticating with the Data Streams API in various languages. Each example shows how to properly generate the required headers and make a request.
 
-- [JavaScript examples](/data-streams/reference/authentication/javascript-examples)
-- [TypeScript examples](/data-streams/reference/authentication/typescript-examples)
-- [Go examples](/data-streams/reference/authentication/go-examples)
-- [Rust examples](/data-streams/reference/authentication/rust-examples)
+- [JavaScript examples](/data-streams/reference/data-streams-api/authentication/javascript-examples)
+- [TypeScript examples](/data-streams/reference/data-streams-api/authentication/typescript-examples)
+- [Go examples](/data-streams/reference/data-streams-api/authentication/go-examples)
+- [Rust examples](/data-streams/reference/data-streams-api/authentication/rust-examples)
 
 ## Common Authentication Errors
 
@@ -130,8 +131,8 @@ When working with the Data Streams API, the most common authentication issues in
 
 For complete information on all possible error responses:
 
-- [REST API Error Response Codes](/data-streams/reference/interface-api#error-response-codes)
-- [WebSocket Error Response Codes](/data-streams/reference/interface-ws#error-response-codes)
+- [REST API Error Response Codes](/data-streams/reference/data-streams-api/interface-api#error-response-codes)
+- [WebSocket Error Response Codes](/data-streams/reference/data-streams-api/interface-ws#error-response-codes)
 
 ## Troubleshooting Authentication
 

…e/authentication/javascript-examples.mdx …i/authentication/javascript-examples.mdxsrc/content/data-streams/reference/authentication/javascript-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/javascript-examples.mdx src/content/data-streams/reference/authentication/javascript-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/javascript-examples.mdx

@@ -15,9 +15,9 @@ import DataStreams from "@features/data-streams/common/DataStreams.astro"
 
 Below are complete examples for authenticating with the Data Streams API in JavaScript, using Node.js. Each example shows how to properly generate the required headers and make a request.
 
-To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/authentication) page.
+To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/data-streams-api/authentication) page.
 
-**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/go-sdk) or [Rust SDK](/data-streams/reference/rust-sdk), you don't need to implement the authentication logic manually.
+**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) or [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk), you don't need to implement the authentication logic manually.
 
 ## API Authentication Example
 

…ference/authentication/rust-examples.mdx …ams-api/authentication/rust-examples.mdxsrc/content/data-streams/reference/authentication/rust-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/rust-examples.mdx src/content/data-streams/reference/authentication/rust-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/rust-examples.mdx

@@ -15,9 +15,9 @@ import DataStreams from "@features/data-streams/common/DataStreams.astro"
 
 Below are complete examples for authenticating with the Data Streams API in Rust. Each example shows how to properly generate the required headers and make a request.
 
-To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/authentication) page.
+To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/data-streams-api/authentication) page.
 
-**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/go-sdk) or [Rust SDK](/data-streams/reference/rust-sdk), you don't need to implement the authentication logic manually.
+**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) or [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk), you don't need to implement the authentication logic manually.
 
 ## API Authentication Example
 
@@ -229,7 +229,7 @@ While this example demonstrates the authentication mechanism, production applica
 - **Resource management**: Implement graceful shutdown for long-running connections
 - **Testing**: Add unit tests for HMAC generation and integration tests for API calls
 
-For production use, consider using the [Rust SDK](/data-streams/reference/rust-sdk) which handles authentication automatically and provides built-in fault tolerance.
+For production use, consider using the [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk) which handles authentication automatically and provides built-in fault tolerance.
 
 ## WebSocket Authentication Example
 
@@ -530,4 +530,4 @@ While this example demonstrates WebSocket authentication, production application
 - **Graceful shutdown**: Properly close WebSocket connections with close frames
 - **Testing**: Add tests for connection handling and message parsing
 
-For production use, consider using the [Rust SDK](/data-streams/reference/rust-sdk) which handles authentication automatically and provides built-in fault tolerance.
+For production use, consider using the [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk) which handles authentication automatically and provides built-in fault tolerance.

…e/authentication/typescript-examples.mdx …i/authentication/typescript-examples.mdxsrc/content/data-streams/reference/authentication/typescript-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/typescript-examples.mdx src/content/data-streams/reference/authentication/typescript-examples.mdx renamed to src/content/data-streams/reference/data-streams-api/authentication/typescript-examples.mdx

@@ -15,9 +15,9 @@ import DataStreams from "@features/data-streams/common/DataStreams.astro"
 
 Below are complete examples for authenticating with the Data Streams API in TypeScript, using Node.js. Each example shows how to properly generate the required headers and make a request.
 
-To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/authentication) page.
+To learn more about the Data Streams API authentication, see the [Data Streams Authentication](/data-streams/reference/data-streams-api/authentication) page.
 
-**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/go-sdk) or [Rust SDK](/data-streams/reference/rust-sdk), you don't need to implement the authentication logic manually.
+**Note**: The Data Streams SDKs handle authentication automatically. If you're using the [Go SDK](/data-streams/reference/data-streams-api/go-sdk) or [Rust SDK](/data-streams/reference/data-streams-api/rust-sdk), you don't need to implement the authentication logic manually.
 
 ## API Authentication Example