Top Builders

Explore the top contributors showcasing the highest number of app submissions within our community.

Kraken REST API

The Kraken REST API provides HTTP-based access to Kraken's spot and futures markets, account data, and trading operations. It covers public market data endpoints (no authentication required) and private endpoints for account management and order execution (HMAC-SHA512 authenticated). The API supports Spot, Futures, Custody, and Embed products, each with separate base URLs.

General
DeveloperKraken (Payward Inc.)
TypeREST API
LicenseCommercial API (free with Kraken account)
Documentationdocs.kraken.com
GitHubkrakenfx/api-go

Core Features

  • Public and private endpoints: public market data requires no authentication; private endpoints use HMAC-SHA512 signing.
  • Multiple product APIs: Spot, Futures, Custody, and Embed each have dedicated endpoints.
  • Tiered rate limiting: per-API-key counter with decay rates based on account tier (Intermediate or Pro).
  • Subaccount support: master accounts can manage subaccounts programmatically.
  • Earn and staking: endpoints for managing yield-generating positions.

Endpoints

Spot REST base URL: https://api.kraken.com/0/

CategoryEndpoints
PublicTicker, OHLC, order book, recent trades, spreads, asset pairs, system status
Private: AccountBalance, trade balance, open/closed orders, trade history, ledger entries
Private: TradingAdd order, amend order, cancel order, cancel all orders, batch orders
Private: FundingDeposit addresses, deposit methods, withdrawal info, withdraw funds
Private: EarnStaking and yield positions

Authentication

Spot REST authentication uses HMAC-SHA512:

  1. Generate a nonce (always-increasing unsigned 64-bit integer; millisecond UNIX timestamps recommended)
  2. Compute: SHA256(nonce + POST body data)
  3. Compute: HMAC-SHA512(URI path + SHA256 result, base64-decoded private key)
  4. Send API-Key header (public key) and API-Sign header (base64-encoded HMAC result)

The private key is never transmitted directly.


Rate Limits (Spot REST)

TierMax CounterDecay Rate
Intermediate200.5 per second
Pro201 per second

Ledger and trade history calls add 4 to the counter; all other private calls add 1. Order placement and cancellation use a separate trading rate limiter. Exceeding limits returns EAPI:Rate limit exceeded. Rate limits are shared across REST, WebSocket, and FIX for the same API key.


Tools and Resources


Ecosystem and Integrations

  • API keys are generated in Kraken account settings with configurable permissions (read-only, trading, funding).
  • Commercial redistribution of Kraken market data requires prior approval from marketdata@kraken.com.
  • Community SDKs available for Python, Go, C++, and Julia (listed in official documentation).

Generate API keys in your Kraken account settings and follow the REST quickstart to place your first programmatic order.

kraken rest api AI technology Hackathon projects

Discover innovative solutions crafted with kraken rest api AI technology, developed by our community members during our engaging hackathons.

AI Classroom Edge Intelligence

AI Classroom Edge Intelligence

AI Classroom Edge Intelligence is a privacy-first classroom AI platform built for schools that need useful AI without sending every piece of student information to the cloud. The platform evaluates each task by privacy level, connectivity, and complexity, then routes it to Offline Edge Mode, a Local Classroom Server, or Fireworks AI Cloud Assist. Sensitive or restricted information stays local. Eligible anonymized, high-complexity tasks are sent through a secure Express backend to Fireworks Serverless using Qwen3.7 Plus. The project includes an AMD Model Router, Edge Runtime Monitor, Rural Connectivity Simulator, Privacy and Local Data Ownership Console, Classroom Digital Twin, and teacher approval workflow. Live results display the provider, model, route, privacy classification, latency, safety note, and AI response. API keys remain server-side, and the privacy guard blocks sensitive requests from cloud inference. The project was inspired by rural schools where connectivity can be unreliable and student privacy is critical. Instead of acting as a simple chatbot, it serves as an intelligent routing and decision-support system. Teachers review, edit, approve, or reject recommendations before instructional actions are recorded. The current implementation includes a working browser interface, real backend routing, live Fireworks Serverless integration, server-side key protection, and Docker containerization. Local AMD AI PC inference, GPU/NPU acceleration, device telemetry, and production synchronization are clearly identified as future work. The long-term vision is a school-owned AI platform combining local intelligence, optional cloud reasoning, persistent classroom evidence, and teacher oversight for rural and underserved communities.

ReproForge Sentinel — Claim-to-Evidence AI

ReproForge Sentinel — Claim-to-Evidence AI

AI systems can generate benchmark claims, model promises, and technical demonstrations faster than teams can verify them. ReproForge Sentinel closes that trust gap by turning an AI/ML claim into structured, inspectable evidence. A user submits a repository URL, the exact claim, a runtime target, and declared security policies. ReproForge evaluates the available claim metadata and policy signals, applies deterministic ShadowGuard risk and reproducibility scoring, records a trace of the evaluation, and produces a Reproducibility Passport. The Passport contains the verdict, evidence chain, missing proof, blocked actions, integrity hashes, security notes, and exportable JSON/PDF results. The hackathon build combines a premium React and TanStack interface with a FastAPI backend, Docker packaging, tests, proof schemas, and AMD/Gemma integration adapters. It also includes an AMD ROCm capture workflow that accepts hardware evidence only when device identity, HIP/ROCm, AMD SMI telemetry, workload metrics, and artifact hashes are successfully captured. Our guided sample is clearly labeled and designed for a reliable judge walkthrough. The current public MVP evaluates submitted claim metadata and declared policies; it does not yet clone or execute arbitrary repositories. Real Fireworks/Gemma inference and direct AMD ROCm telemetry remain explicitly marked pending when verified runtime provenance is unavailable. ReproForge never replaces missing measurements with invented proof. ReproForge is not a “truth machine.” It is an evidence machine: a verification layer for AI teams, security reviewers, researchers, investors, and judges who need to understand what was checked, what passed, what failed, and what still cannot be proven.