API Reference · v1
The unified
transaction API.
One endpoint, every payment platform. Valverna normalizes transactions from Stripe, Klarna, Swish, Shopify and more into a single canonical schema — so your accounting, tax, and ledger integrations only need to speak one language.
Base URL
https://api.valverna.com/v1Release
2026.06 · Schema v2.1
Quickstart
Three steps to read your first transaction through the Valverna API.
Conventions
The Valverna API is built on a handful of consistent rules. Once you learn them for one endpoint, they apply everywhere.
JSON everywhere
All requests and responses are JSON. Field names are camelCase, dates are ISO 8601 with timezone, and all monetary amounts are integer minor units (öre, cents) — never decimal strings.
Bearer auth
Every request carries an Authorization: Bearer header — a vlv_ app access token or a vlvk_ personal API key.
Keyset pagination
List endpoints return a nextCursor — the id of the last item — which you pass back as startAfter. No offset, no total count.
Predictable errors
Errors return standard HTTP codes with an error object carrying a code and message. Validation failures return 422 with a list of per-field issues.
Idempotent writes
POST endpoints accept an Idempotency-Key header. Replays return the existing document. Safe to retry.
Pricing
You prepay a balance and it's drawn down per delivered transaction — each transaction your app reads
(webhook delivery, once live, draws down the same way). Reads past a zero balance return 402 until you top up.
Authorizing businesses, connecting platforms, and authorization flows are all free.
$0.001 /transaction
Flat rate. All endpoints, webhooks, OAuth, unlimited apps. Top up a balance, drawn down per delivered transaction.
Custom
Negotiated rate, invoiced billing, SLA, dedicated support, SSO, and custom data retention.
Contact us