Stable identities
Keep supported transaction and movement references for repeatable reads and deduplication in the consumer.
Normalized Transaction API / synthetic sandbox
Technical movements.
A consistent contract.
Normalize supported transaction evidence into a versioned customer contract. Exact amounts, source references and explicit range boundaries travel with the result.
In development · no public production endpoint
CONTRACT DIRECTIONILLUSTRATIVE
{
"amountAtomic": "1000000000000000000",
"source": "synthetic-fixture",
"historyComplete": false,
"automaticCorrection": false,
"transactionsWritten": 0
}This example explains a design principle. It is not a live API response or a stable production schema.
06 / Why this matters
Useful structure should preserve the source.
A normalised technical movement should retain its chain, transaction and event identity. It does not automatically establish an economic interpretation, a tax treatment or a full lifetime history.
Source evidence and interpretation should travel together. A downstream product must be able to distinguish observed data, a supported interpretation and an unresolved question.
The intended contract
Exact amounts
Preserve atomic integer strings and separate chain/contract identity from symbols, decimals and valuation.
Scoped access
The local SDK 1.1 and customer preview use signed requests, project scopes and revocable identities. Public key issuance and production import access remain disabled.
USE CASES / Built for technical teams
A better basis for your product.
CoinTaxReporting
First customer direction, with a developed signed client and separate review workflow.
Wallet products
Build a bounded activity view that keeps source evidence and unknown events visible.
External B2B
Future customer integrations through the same versioned contract after production acceptance.
What is available today?
The local transaction API and CTR connection are tested using synthetic or captured fixtures. A real-data ingestion adapter, production backfills and a public transaction import service have not been released. AWS and BigQuery source integrations are planned.
Read the implementation statusQUESTIONS / Normalized Transaction API
Before you build.
Is the public transaction import active?
No. Public accounts, real-data acquisition and production CTR activation require separate release acceptance.
Is a page a complete wallet history?
No. A bounded result page must be read together with its requested range, coverage and missing intervals.
Does Indexbase classify taxes or execute trades?
No. Technical data, bookkeeping, tax reports and trading execution remain separate responsibilities.
Built with a long view
Help shape the next
layer of blockchain data.
Explore the direction. Early access is not open yet.