We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Add 'Debug an auth failure end-to-end' recipe Pattern for diagnosing the most common SDK auth failures: - SDK-version sanity (catches users on the broken 0.4.0-alpha.1) - Token shape sanity (40 chars) - Authenticated probe with branched error handling for UNAUTHORIZED, FORBIDDEN (with IP-allowlist guidance), and the gateway-level 405 'Missing Authentication Token' that alpha.1 produced. Output is meant to be the next action in plain English so a user hitting auth issues knows what to fix without reading the full Authentication wiki page first.
Fix auth header docs: access-token, not Authorization: Bearer Cryptohopper Public API v1 uses 'access-token: <token>', not the OAuth2-conventional 'Authorization: Bearer <token>'. The gateway in front of api.cryptohopper.com/v1/* rejects Bearer with a SigV4 parse error. See cryptohopper-resources#9.
Drop incorrect 'public, no auth needed' claims (issue #9) E2E smoke test against the live API found that every Cryptohopper v1 endpoint requires a valid OAuth bearer — the AWS API Gateway in front of the production API rejects unauthenticated calls (returns 405 Missing Authentication Token), even on routes conceptually treated as 'public market data' like /exchange/ticker and /market/homepage. Replaces the incorrect 'pass an empty string for public endpoints' guidance with the actual behaviour. See cryptohopper-resources#9 for the full investigation.
Add Comparison page: same operations side-by-side across all 9 SDKs Cross-language reference for picking an SDK or porting between languages. Eight tables covering: client construction, user.get, hoppers.list, exchange.ticker (public), backtest.create, error catching, custom HTTP transport injection, retry disabling. Plus a 'picking an SDK' section that points users at the right SDK based on their runtime, and a public-endpoint anonymity note. Linked from Home Quick Links and the _Sidebar.
Add _Sidebar with cross-page and cross-SDK navigation Renders on every wiki page so users can jump between Home/Auth/Errors/Rate-Limits/Recipes without round-tripping through Home, and to any sibling-language SDK wiki.
Add Recipes page; add Swift to Sibling SDKs Recipes.md collects ten copyable patterns (backtest polling, fill detection, custom fetch, serverless tuning, etc.). Home now links it from Quick Links. Sibling table updated to add Swift, which was missing from the prose listing and the table.
Sync wiki content from main repo docs/
Initial Home page