Kraken Spot REST API

Name: Kraken Spot REST API API
Brand: Kraken Spot REST API
Availability: InStock

★ Only Publicly Available OpenAPI DocumentFinanceBankingapiKey41 EndpointsREST

For Agents

Trade spot crypto on Kraken — fetch market data, place and cancel orders, manage balances, deposits, and withdrawals — with API key plus signed-request authentication.

Quickstart

Get started with Kraken Spot REST API in minutes using your preferred integration method.

# Add to your MCP client config (Claude Desktop, Cursor, Windsurf)
{
  "jentic": {
    "url": "https://api.jentic.com/mcp",
    "auth": "oauth"
  }
}

# Then ask your agent:
"place a spot order on kraken"

# → Jentic returns the GET /events tool with parameter schema, agent executes.

Capabilities

What an agent can do with Kraken Spot REST API API.

Place, amend, cancel, and batch-manage spot orders on Kraken trading pairs

Fetch ticker, OHLC, order book depth, and recent trades for any tradable asset pair

Retrieve authenticated account, trade, and extended balance snapshots

List open and closed orders, trade history, ledger entries, and open margin positions

GET STARTED

Start building with Kraken Spot REST API API

Explore with Jentic

View OpenAPI Document

Jentic publishes the only available OpenAPI document for Kraken Spot REST API, keeping it validated and agent-ready.

Jentic publishes the only available OpenAPI specification for Kraken Spot REST API, keeping it validated and agent-ready. The Kraken Spot REST API exposes 41 endpoints for the Kraken cryptocurrency exchange covering public market data, authenticated account balances, spot order placement and cancellation, deposits, withdrawals, internal wallet transfers, and Earn allocation strategies. Public endpoints return ticker, OHLC, order book depth, and asset pair metadata, while private endpoints require an API key plus an HMAC request signature in dedicated headers and use POST with form-encoded bodies. The spec is split into /public and /private path prefixes that match Kraken's documented signing model.

Use Cases

Patterns agents use Kraken Spot REST API API for, with concrete tasks.

★ Algorithmic spot trading

A trading bot reads OHLC and order book data from Kraken's public endpoints, then places limit and market orders against the private /AddOrder endpoint with HMAC signing. Risk controls use /OpenOrders and /TradeBalance to size positions, and /CancelAll provides a kill switch. Building this directly takes 1-2 weeks for signing, retry, and rate-limit handling; through a structured client it drops to a few days.

Place a limit buy order via POST /private/AddOrder for pair 'XBTUSD', volume 0.05, price 60000, ordertype 'limit' and confirm the txid in the response.

Portfolio reporting and reconciliation

An accounting workflow pulls balance, ledger, and trade history from /Balance, /Ledgers, and /TradesHistory to reconcile crypto holdings, realised P&L, and fees against an internal ledger. Kraken returns paginated, timestamped entries that map cleanly onto cost-basis tools. This pattern is widely used by funds and high-volume retail traders for tax reporting.

Call POST /private/TradesHistory with start and end timestamps for the last quarter, then aggregate trade volumes by pair and report total fees paid.

Treasury withdrawals and transfers

A treasury system uses /WithdrawMethods, /WithdrawAddresses, /WithdrawInfo, and /Withdraw to move funds to whitelisted external wallets, or /WalletTransfer to move balances between Spot and Futures wallets. /WithdrawStatus and /WithdrawCancel provide visibility and a backstop for in-flight transactions. Kraken enforces address whitelisting, so the API surface assumes prior account configuration.

Initiate a withdrawal via POST /private/Withdraw with asset 'USDC', key '<whitelist-key>', amount '500' and poll POST /private/WithdrawStatus until the status is 'Success'.

Agent-driven trading workflows via Jentic

An agent searches Jentic for 'place a kraken order' and is matched to POST /private/AddOrder along with its required parameters. Jentic injects the API key and HMAC signature so the agent never handles the secret directly, and the agent can compose multi-step workflows like fetch ticker, evaluate spread, place order, and confirm execution.

Use Jentic to load kraken_place_order, then execute it for pair 'ETHUSD', volume 0.5, ordertype 'limit', price 3000 and return the txid.

Key Endpoints

41 endpoints — jentic publishes the only available openapi specification for kraken spot rest api, keeping it validated and agent-ready.

METHOD

PATH

DESCRIPTION

GET

/public/Ticker

Get ticker information for a pair

GET

/public/OHLC

Get OHLC candle data

GET

/public/Depth

Get order book depth

POST

/private/Balance

Get account balance

POST

/private/AddOrder

Place a spot order

POST

/private/CancelOrder

Cancel a single order

POST

/private/Withdraw

Withdraw funds to a whitelisted address

POST

/private/Earn/Allocate

Allocate funds to an Earn strategy

GET

/public/Ticker

Get ticker information for a pair

GET

/public/OHLC

Get OHLC candle data

GET

/public/Depth

Get order book depth

POST

/private/Balance

Get account balance

POST

/private/AddOrder

Place a spot order

POST

Why though Jentic?

Three things that make agents converge on Jentic-routed access.

Credential isolation

Kraken API keys and the matching private signing secrets are stored encrypted in the Jentic vault (MAXsystem). Jentic computes the HMAC-SHA512 signature per request, so the secret never enters the agent's context window.

Intent-based discovery

Agents search Jentic by intent (e.g. 'place a kraken order', 'fetch kraken balance') and receive the matching /public or /private operation with its parameter schema, so signing requirements are abstracted away.

Time to first call

Direct Kraken integration: 1-2 weeks for HMAC signing, nonce management, and retry semantics. Through Jentic: under a day — search, load schema, execute.

Related APIs

Alternatives and complements available in the Jentic catalogue.

Alternative

Binance

Higher-volume spot exchange with broader pair coverage and similar order endpoints

Choose Binance when liquidity for non-USD pairs or altcoin coverage matters more than US regulatory clarity.

Alternative

KuCoin

Spot and margin exchange with similar private-key-plus-passphrase signing model

Choose KuCoin when targeting a wider altcoin selection or margin endpoints.

Alternative

Gemini

US-regulated spot exchange with REST trading and custody endpoints

Choose Gemini when US regulatory standing and custody features outweigh raw pair coverage.

Complementary

CoinGecko

Cross-exchange market data for price comparison alongside Kraken trading

Use CoinGecko alongside Kraken to validate pricing across venues before placing orders.

FAQs

Specific to using Kraken Spot REST API API through Jentic.

Why is there no official OpenAPI spec for Kraken Spot REST API?

Kraken does not publish an OpenAPI specification. Jentic generates and maintains this spec so that AI agents and developers can call Kraken Spot REST API via structured tooling. It is validated against the live API and kept up to date. Get started at https://app.jentic.com/sign-up.

What authentication does the Kraken Spot REST API use?

Private endpoints require two headers — an API key and an HMAC-SHA512 request signature derived from the nonce, request body, and URI path. The spec exposes both as apiKey schemes (ApiKeyAuth and ApiSignAuth). Jentic handles the signing flow inside MAXsystem so the agent never sees the secret key.

Can I place limit and market orders with the Kraken Spot REST API?

Yes. POST /private/AddOrder accepts ordertype 'limit', 'market', 'stop-loss', 'take-profit', and other variants documented in the spec. POST /private/AddOrderBatch sends multiple orders in a single signed request, and POST /private/AmendOrder modifies a working order without cancellation.

What are the rate limits for the Kraken Spot REST API?

Kraken applies a tiered counter system per account where each call adds to a decay counter and order operations carry higher cost than market data. The exact ceilings depend on verification tier — refer to support.kraken.com for your account's limits and design retries with exponential backoff.

How do I place a spot order through Jentic?

Search Jentic for 'place a kraken order', load POST /private/AddOrder, and execute it with pair, volume, ordertype, and price. Install with pip install jentic and Jentic injects the signed Authorization headers automatically.

Does the Kraken Spot REST API cover futures and margin trading?

This spec covers the Spot REST API only. Kraken Futures uses a separate API surface, and margin-specific operations such as /OpenPositions return data for spot-margin positions only — futures derivatives are out of scope here.