Skip to main content

An API request returns 401

Confirm the header is Authorization: Bearer YOUR_API_KEY. The key may be malformed, revoked, expired, or attached to an account without current API access. Rotate it from API keys if needed.

An API request returns 403

Check the response error:
  • insufficient_scope: the key does not include the endpoint’s scope.
  • ip_not_allowed: the request’s outbound IP is outside the key allowlist.

An API request returns 429

Reduce request rate or concurrency. If quota_exhausted is returned, inspect GET /api/v1/usage and the current account plan.

A signal is visible but no copied order appears

Copy-ready means the signal is available for account evaluation, not that an order is guaranteed. Check that the account is running and review signed limits, position capacity, collateral, entry conditions, and venue status. Do not re-enroll or paste the API-agent key again unless the product explicitly requires a new credential.

Copy Trade shows recovery or credential attention

Do not delete account records or bypass the product flow. Keep protective controls available, use Pause or Emergency Flatten only as intended, and follow the authenticated revoke or replacement steps shown in the account panel.

Data looks stale or incomplete

Check generatedAt, observedAt, coverage, and degraded indicators. A missing value means unknown; it should not be converted to zero.
Never send credentials to anyone who claims they need them to troubleshoot your account.