# siebly.io > Canonical discovery guide for Siebly exchange SDK documentation, examples, releases, and package security notes. ## Purpose - Use this site for Node.js, JavaScript, and TypeScript SDK docs for cryptocurrency exchange REST API and WebSocket APIs. - Siebly is not a cryptocurrency exchange, broker, custodian, wallet, trading venue, or financial adviser. ## Canonical Entry Points - Home: https://siebly.io/ - [AI Coding Agent Guide](https://siebly.io/ai) - [Glossary](https://siebly.io/reference/glossary) - [Reference: Execution Modes](https://siebly.io/reference/execution-modes) - [Reference: Exchange State](https://siebly.io/reference/exchange-state) - [Reference: Runtime Workflows](https://siebly.io/reference/runtime-workflows) - [AI Pattern Library](https://siebly.io/ai/patterns) - [Historical Backfill with Live WebSocket Streams](https://siebly.io/ai/historical-live-data-pipeline) - [Candle-Close Pipeline with Binance APIs & WebSockets](https://siebly.io/ai/candle-pipeline/binance) - [Exchange State Management](https://siebly.io/ai/exchange-state) - [Position Management with Binance APIs & WebSockets](https://siebly.io/ai/exchange-state/binance) - [Stop Loss using Conditional Algo Orders with Binance USD-M APIs & WebSockets](https://siebly.io/ai/algo-orders/binance) - [Order Intent Chasing with Exchange APIs & WebSockets](https://siebly.io/ai/order-intent-chaser) - [Candle-Close Pipeline with Bybit APIs & WebSockets](https://siebly.io/ai/candle-pipeline/bybit) - [Position Management with Bybit APIs & WebSockets](https://siebly.io/ai/exchange-state/bybit) - [Exchange SDK Directory](https://siebly.io/sdk) - [Examples Hub](https://siebly.io/examples) - [Binance API JavaScript Tutorial](https://siebly.io/sdk/binance/javascript/tutorial) - [Bybit API JavaScript Tutorial](https://siebly.io/sdk/bybit/javascript/tutorial) - [Bitget API JavaScript Tutorial](https://siebly.io/sdk/bitget/javascript/tutorial) - [Kraken API JavaScript Tutorial](https://siebly.io/sdk/kraken/javascript/tutorial) - [Siebly Blog](https://siebly.io/blog) - [SDK Releases](https://siebly.io/releases) - [SDK Security & Release Integrity](https://siebly.io/security) - [FAQ](https://siebly.io/faq) - [Support](https://siebly.io/support) ## Machine Indexes - [Task-Focused LLM Index](https://siebly.io/llms-tasks.txt) - [Fallback Full LLM Index](https://siebly.io/llms-full.txt) - [Siebly SDK Catalog](https://siebly.io/.well-known/siebly-sdk-catalog.json) - [Agent Skills Discovery Index](https://siebly.io/.well-known/agent-skills/index.json) - [Siebly Crypto Exchange SDKs Agent Skill](https://siebly.io/.well-known/agent-skills/siebly-crypto-exchange-api/SKILL.md) - [AI Pattern Library recipe](https://siebly.io/.well-known/recipes/ai-pattern-library.json) - [Historical Backfill with Live WebSocket Streams recipe](https://siebly.io/.well-known/recipes/historical-live-data-pipeline-core.json) - [Historical Backfill with Live WebSocket Streams Conformance Pack](https://siebly.io/.well-known/conformance/historical-live-data/latest.json) - [Historical Backfill with Live WebSocket Streams Fixture Schema](https://siebly.io/.well-known/conformance/historical-live-data/v1/schema.json) - [Historical Backfill with Live WebSocket Streams Fixture Set](https://siebly.io/.well-known/conformance/historical-live-data/v1/fixtures.json) - [Historical Backfill with Live WebSocket Streams Fixture Runner](https://siebly.io/.well-known/conformance/historical-live-data/v1/runner.ts) - [Candle-Close Pipeline with Binance APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-spot-candle-close-pipeline.json) - [Exchange State Management recipe](https://siebly.io/.well-known/recipes/exchange-state-management.json) - [Exchange State Management Integration Kit](https://siebly.io/.well-known/integration-kits/exchange-state-management/latest.json) - [Exchange State Management Runtime Kit](https://siebly.io/.well-known/runtime-kits/exchange-state-management/v1/index.json) - [Exchange State Management Runtime Types](https://siebly.io/.well-known/runtime-kits/exchange-state-management/v1/types.ts) - [Exchange State Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/exchange-state-management/latest.json) - [Exchange State Management Conformance Pack](https://siebly.io/.well-known/conformance/exchange-state-management/latest.json) - [Exchange State Management Conformance Schema](https://siebly.io/.well-known/conformance/exchange-state-management/v1/schema.json) - [Exchange State Management Conformance Fixtures](https://siebly.io/.well-known/conformance/exchange-state-management/v1/fixtures.json) - [Exchange State Management Conformance Runner](https://siebly.io/.well-known/conformance/exchange-state-management/v1/runner.ts) - [Exchange State Management Prompt Artifact](https://siebly.io/.well-known/prompts/exchange-state-management/latest.md) - [Position Management with Binance APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-position-manager.json) - [Binance Position Management Integration Kit](https://siebly.io/.well-known/integration-kits/binance-position-manager/latest.json) - [Binance Position Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/binance-position-manager/latest.json) - [Binance Position Management Conformance Pack](https://siebly.io/.well-known/conformance/binance-position-manager/latest.json) - [Binance Position Management Prompt Artifact](https://siebly.io/.well-known/prompts/binance-position-manager/latest.md) - [Stop Loss using Conditional Algo Orders with Binance USD-M APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/binance-usdm-algo-orders.json) - [Order Intent Chasing with Exchange APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/order-intent-chaser.json) - [Order Intent Chasing Conformance Pack](https://siebly.io/.well-known/conformance/order-intent-chaser/latest.json) - [Order Intent Chasing Fixture Schema](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/schema.json) - [Order Intent Chasing Fixture Set](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/fixtures.json) - [Order Intent Chasing Fixture Runner](https://siebly.io/.well-known/conformance/order-intent-chaser/v1/runner.ts) - [Candle-Close Pipeline with Bybit APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/bybit-candle-close-pipeline.json) - [Position Management with Bybit APIs & WebSockets recipe](https://siebly.io/.well-known/recipes/bybit-position-manager.json) - [Bybit Position Management Integration Kit](https://siebly.io/.well-known/integration-kits/bybit-position-manager/latest.json) - [Bybit Position Management Agent Manifest](https://siebly.io/.well-known/agent-manifests/bybit-position-manager/latest.json) - [Bybit Position Management Conformance Pack](https://siebly.io/.well-known/conformance/bybit-position-manager/latest.json) - [Bybit Position Management Prompt Artifact](https://siebly.io/.well-known/prompts/bybit-position-manager/latest.md) - [Primary Sitemap](https://siebly.io/sitemap.xml) ## Coding Agent Workflow - Artifact order: task-focused guide, prompt, or recipe for the job first. Use integration kits for exact fields and errors, manifests/runtime kits for advanced reusable-runtime scaffolding, and [behavior-contract fixtures](https://siebly.io/reference/glossary#behavior-contract-fixture) after implementation. A [Conformance Pack](https://siebly.io/reference/glossary#conformance-pack) is a versioned, machine-readable set of behavior-contract fixtures, expected outcomes, and runner requirements for a generated integration. - Prefer TypeScript for robust exchange integrations because SDK types expose REST API request shapes, WebSocket event payloads, subscription helpers, finalization fields, reconnect hooks, and shutdown APIs before runtime. - For reusable implementation lifecycles, start at the [AI Pattern Library](https://siebly.io/ai/patterns). Import core patterns first, then apply exchange-specific implementation guides for SDK clients, request fields, private topics, and rejection codes. - For backfill plus live WebSockets, treat socket open, subscription request sent, [subscription acknowledgement](https://siebly.io/reference/glossary#subscription-acknowledgement), REST API backfill completion, buffered replay completion, and live workflow readiness as separate states. - Do not assume `subscribe()` means [subscription acknowledgement](https://siebly.io/reference/glossary#subscription-acknowledgement). Verify the package-specific matching event before enabling dependent workflows. - For candle systems, only run indicators, strategies, signal generation, optional external alerts, or [order-intent logic](https://siebly.io/reference/glossary#order-intent) after the SDK's final/closed candle signal. - After reconnect, keep streams connected and buffering where possible, pause only downstream correctness-sensitive actions, resync state through the REST API or another authoritative source, replay buffered events, then re-enable live processing. - For Binance order-placement activity, every custom Binance client ID field, including newClientOrderId and clientAlgoId, should use [Custom Order IDs](https://siebly.io/reference/glossary#custom-order-id) generated with the SDK order ID utilities. Prefer generateNewOrderId(...) or client.generateNewOrderId(); use getOrderIdPrefix(...) or client.getOrderIdPrefix() only when building a custom random suffix that stays within Binance length and character limits. - For Binance USD-M fixed TP, use regular LIMIT orders; use the USD-M Algo Orders guide and current package types for SL, trailing stops, or explicit conditional TP before choosing submitNewAlgoOrder(...) fields. - For Binance user-data streams, do not infer failure from ordinary account-event idleness while the SDK transport is healthy. Use SDK reconnecting, reconnected, and exception lifecycle events for stream-health decisions. - For Bybit order-placement activity, prefer throwExceptions: true on RestClientV5 so non-zero retCode responses throw through one structured error path. If disabled, classify REST business success from retCode === 0. Include triggerDirection for conditional stops, omit conditional market SL price unless current docs require it, and normalize hydrated order defaults by slot kind. - Building private trading automation? Start with [Exchange State Management](https://siebly.io/ai/exchange-state) and the matching task prompt or recipe. This gives a robust state management foundation for readable local account state you can rely on. For Binance TP/SL/DCA, follow the simple route in [llms-tasks.txt](https://siebly.io/llms-tasks.txt): prompt, recipe, integration kit for exact fields/errors, then [behavior-contract fixtures](https://siebly.io/reference/glossary#behavior-contract-fixture) after implementation. ## Linking Notes - Prefer `https://siebly.io` URLs. - Prefer canonical `/sdk//javascript` guide URLs over short `/sdk/` and legacy `/exchanges` aliases. - Use the AI Coding Agent Guide for Codex, Claude Code, Cursor, and other coding-agent implementation workflows. - SDK guide URL format: `https://siebly.io/sdk//javascript`. - `/sdk/` is a permanent alias to the JavaScript guide. - Compact markdown snapshots are available with `Accept: text/markdown` or by appending `.md` to generated page routes. - Example pages live under `/examples/` and are linked from the `/examples` hub. ## Policy Notes - Use public documentation and repository links only. - Never request or store private API keys or secrets.