polyhub_copy

Automating copy-trading tasks via an API key involves configuring environment variables for your base URL and key, then executing deterministic commands to create, update, or delete copy tasks without manual UI interaction.

Managing take-profit and stop-loss rules for copy tasks requires applying per-market and per-task constraints through API commands, ensuring strict validation for IDs to enforce safety rules during batch operations.

You can batch update copy positions and sell trades using the API by enforcing deterministic tool commands with strict ID validation, allowing guided inspection and execution of trades against your account.

Checking total PnL and signals for your copy-trading portfolio involves executing API commands to review positions and trades, applying pre-flight balance checks to validate safety before retrieving financial data.

You need to set environment variables, specifically the API base URL and API key, to authenticate and establish connectivity before listing or managing any copy-trading tasks programmatically.

Limitations when deleting copy tasks via API commands include strict validation requirements for specific IDs like taskId, ensuring deterministic execution through curl and jq to prevent accidental invalid batch deletions.