Changelog

v1 · November 2026#

The first version of the Myntkaup public API, opening to accounts step by step.

• Authentication with Ed25519-signed requests. Keys are created in the webapp under Settings → API, after an electronic ID check, with scopes, an optional IP allowlist and an expiry of up to a year, or none.
• Scopes: account:read, transactions:read, trade, giftcards:create and withdrawals:create.
• Market data: GET/v1/assets, GET/v1/prices and GET/v1/prices/{asset}, at your account tier.
• Account: GET/v1/me, GET/v1/balances and GET/v1/limits.
• Trading: quotes valid for a few seconds with POST/v1/quotes, accepted with POST/v1/trades. Settled in USDC.
• History: trades from every channel and the full ledger, with cursor pagination.
• Gift cards: create, list and print them as PDFs.
• Withdrawals: from USDC to an Icelandic bank account in your own name, saved or new (POST/v1/withdrawals/bank, GET/v1/bank-accounts), and crypto withdrawals confirmed from your email (POST/v1/withdrawals/crypto).
• Limits: rate limits per key and per account, concurrency caps, and the RateLimit-Policy, RateLimit and Retry-After headers.
• Idempotency keys on trades, gift cards and withdrawals.
• The OpenAPI 3.1 document.

The Node.js SDK (@myntkaup/api) and the command-line tool (@myntkaup/cli) are on npm, at version 0.2.0, and the Python SDK (myntkaup) is on PyPI, at version 0.1.0. Since 0.2.0, a bank withdrawal takes no asset: it is always from USDC.

Being considered#

Not promised, but on the list for after v1: deposit methods and addresses, transaction reports as PDF, XLSX or CSV, price history, webhooks for filled trades and deposits, and a public sandbox. Tell us what you need: myntkaup@myntkaup.is.