Skip to content

Troubleshooting ​

Public request asks for credentials ​

Use getPublicProduct(), getPublicProducts() or getPublicProductBook() for unauthenticated Advanced Trade data. The similarly named methods without Public use authenticated routes.

Authentication fails ​

Confirm API family, permissions, environment, key name, private-key format and clock. Advanced Trade uses CDP key credentials. For another API family, follow its product guide. Preserve PEM newlines. A signer accepting a key does not prove the target product supports its algorithm.

WebSocket opens but no data arrives ​

Listen to response and exception. Check the WS_KEY_MAP value, exact channel and product IDs. Topic parameters belong in payload. Parsed data arrives on update, not the message event used by some other SDKs. Add heartbeats to Advanced Trade subscriptions and distinguish a quiet market from a rejected channel.

Sandbox URL fails ​

Advanced Trade has a static REST sandbox but no WebSocket sandbox. Check environment availability rather than assuming useSandbox applies everywhere.

Order request resolves but no order appears ​

Inspect success and error_response, or preview errs. A preview never submits an order. For submitted orders, check the private stream and resolve remaining ambiguity with a targeted read. Never repeat an uncertain submission blindly.

Proxy works for REST only ​

REST Axios options do not configure WebSocket transport. Set wsOptions.agent as well. Disable SDK keepAlive when supplying a custom HTTPS agent. See Proxies.

Reporting a problem ​

Include the SDK version, runtime or framework version, client, exchange environment and method. For failed requests, include the HTTP status and exchange error code. Add a minimal request example or, for streams, the topic and connection events. Remove credentials, signatures and private account data before sharing.

TypeScript checks ​

The SDK works with both JavaScript and TypeScript. TypeScript is optional, but we strongly recommend it for SDK integrations: the included types help catch invalid method names, parameter shapes and response assumptions at build time, before requests reach the exchange. If you choose TypeScript, follow the TypeScript setup and run npx tsc --noEmit during development and CI. Type checking does not replace runtime validation or exchange-side checks.

Some runtimes can execute TypeScript directly. For example, Node.js type stripping supports erasable TypeScript syntax without a separate compiler, but does not check types. If your runtime cannot execute the syntax used by a TypeScript example, compile that example to JavaScript or use a compatible TypeScript runner. Examples with local .js imports that refer to TypeScript source files can use the compiler-based setup above. Plain JavaScript usage does not need any TypeScript tooling.

Built by Siebly. Open source SDKs for exchange APIs.