Reliable interfaces for turning trading signals into auditable automation.
PipSync publishes the contracts and developer tools around its integration boundary: API descriptions, schemas, SDKs, runnable examples, validation tooling, and deterministic risk calculations. The production execution platform remains a managed service.
Try it without an account: open the PipSync Playground repository to validate a synthetic signal, build a TradingView paper alert, or calculate a position size entirely in your browser.
Ready for managed access? Create a PipSync account or compare plans.
Important
Trading involves risk. The projects here are developer tools, not financial advice, a profit promise, or authorization to place live orders. Examples default to synthetic, mock, or paper-trading data.
| Repository | What it is | First step |
|---|---|---|
pipsync-playground |
Browser-only signal, alert, sizing, and HMAC playground | Run the static demo locally; no account or credential required |
pipsync-api-collections |
Read-only Postman and Bruno collections generated from the public contract | Run the loopback-only synthetic mock |
pipsync-signal-check-action |
Offline GitHub Action for PipSync and TradingView paper payloads | Add one validation step to CI |
pipsync-n8n-templates |
Importable, credential-free n8n workflows for safe evaluation | Import a workflow and use synthetic data first |
n8n-nodes-pipsync |
Read-only n8n community node prepared for npm provenance review | Inspect the release artifact; it is not on npm yet |
pipsync-pine-alerts |
Paper-only TradingView alert templates for Pine Script v6 | Paste a complete script into Pine Editor |
pipsync-mcp |
Local read-only MCP tools for validation and risk math | Run the stdio smoke test without network access |
pipsync-spec |
Sanitized public OpenAPI contract plus versioned JSON Schemas and fixtures | Validate the contracts locally |
pipsync-sdk |
Typed TypeScript and Python clients | Run the no-credential examples |
pipsync-examples |
Copyable integrations and mock/paper workflows | Pick the smallest example for your source |
pipsync-cli |
Local validation, mocks, diagnostics, webhook verification, and loopback-only streams | Run pipsync --help |
pipsync-connector-kit |
Source-connector contract, conformance suite, and in-memory paper sink | Test a normalizer against the harness |
pipsync-risk-math |
Deterministic position-size and risk calculations | Run the test vectors before integrating |
pipsync-signal-bench |
Synthetic multilingual parser evaluation dataset and runner | Score the included predictions |
pipsync-latency-bench |
Reproducible synthetic paper-pipeline latency harness | Start the loopback simulator |
pipsync-mcp-evals |
No-execution MCP mock and trading-tool safety evaluations | Run the deterministic eval suite |
git clone https://github.com/pipsyncio/pipsync-spec.git
cd pipsync-spec
npm ci
npm testThe published REST contract is the source of truth for live API paths. Standalone JSON Schemas are versioned community interchange formats; their presence does not imply that a corresponding live endpoint exists.
Public repositories are designed to make integrations inspectable and reproducible:
- OpenAPI and JSON Schema contracts
- synthetic valid and invalid fixtures
- client-side authentication, pagination, retries, and typed errors
- webhook verification helpers and replay-safe integration patterns
- mock servers, paper-mode examples, and conformance checks
- deterministic calculations with test vectors
The following remain private because they contain service security boundaries or product-specific execution logic:
- production orchestration, tenant authorization, and billing systems
- broker credentials, key-management internals, and live adapter operations
- proprietary parsing prompts, model routing, and trading heuristics
- production risk policy, kill switches, and incident controls
- customer signals, account data, logs, and broker certification evidence
No public example requires a production credential. Never commit API keys, webhook secrets, account identifiers, customer payloads, or live broker configuration.
Please do not report vulnerabilities in public issues. Use the affected repository's Security tab to submit a private advisory; if that is unavailable, use the PipSync support channel.
- General questions: use the central PipSync Discussions
- Product support: pipsync.io/support
- Contribution guide:
pipsyncio/.github
For managed API access and production integration guidance, continue with the PipSync API documentation.
- Contracts before clients.
- Synthetic fixtures before customer data.
- Mock and paper execution before live execution.
- Authentication and idempotency before side effects.
- Explicit uncertainty before performance claims.
© PipSync contributors. Repository-specific licenses apply.