Core pack
Transactions CSV import API
Import ledger or payment transactions from any CSV. Amounts parsed, currency captured, status enum-bounded.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=transactions_v1" \
-F "file=@your_data.csv"Canonical columns
The whole schema, printed as it ships.
Every canonical column, the type each row carries, whether it is required, the field-level validators that fire on commit, and the multilingual header hints the cascade resolves against. This is the shipped definition, not a summary of it.
transactions_v1- fields
- 7
- required
- 3
- validated
- 0
- hints
- 19
| Canonical column | Type | Required | Validators | Header hints the cascade matches |
|---|---|---|---|---|
id | string | yes | — | matched on the column name |
amount | number | yes | — | betragmontantimporteamount |
currency | string | yes | — | währungdevisemonedavaluta |
status | enumpendingsucceededfailedrefunded | — | — | statusstatutestadostato |
customer_id | string | — | — | kundeclientcliente |
created_at | date | — | — | matched on the column name |
description | string | — | — | beschreibungdescriptiondescripcióndescrizione |
Read the same definition as JSON at GET /v1/templates/transactions_v1. A hint match resolves on layer 2 — no LLM call, no token spend, just the flat per-map fee. Hover a validator id to see what it checks.
- 7 canonical fields
- 3 required
- 0 validated
- 19 header hints, 5 languages
Why it exists
Written for the file you actually receive.
The Transactions template lands payment, ledger, and Stripe-export-shaped data into a single canonical row. It is the schema you reach for when a finance team hands you a year of bank reconciliations as CSV, when you migrate off Square mid-quarter, or when a marketplace partner ships you a monthly settlement file. Six fields are enough to carry the entire row through cleanly: id (the payment processor reference), amount (number, locale-tolerant), currency (string, not enum — ISO-4217 is too long to enumerate), status (one of pending / succeeded / failed / refunded), customer_id for the foreign key back to your CRM, and a free-text description that captures the wire memo or invoice line. Teams use the Transactions template for migrations, daily reconciliation pipelines, and to back the customer-facing "download my activity" export.
The amount field accepts US ("1,234.56"), EU ("1.234,56"), and Swiss ("1'234.56") number formats; locale is detected per column, not per cell, so a mixed file is rejected with a clear error rather than silently mis-parsed. The status enum is deliberately small — chargebacks and disputes live in a separate template so the line-item shape does not bloat.
Migration scenarios & the foreign headers they ship
The Transactions template lights up for: monthly Stripe-to-warehouse syncs that feed a finance dashboard, mid-quarter PSP migrations (Stripe → Adyen, Square → Stripe) where you need to backfill the new platform with the old payment history, marketplace settlement file ingestion from Amazon / Etsy / Shopify Payments, and bank-reconciliation imports from SEPA / ACH CSVs. Common foreign headers the cascade resolves at zero cost: "Transaction ID / Betrag / Montant / Importe / Currency / Währung / Devise / Status / Statut / Stato / Customer / Kunde / Cliente / Date / Datum / Description / Beschreibung". The locale-aware number parser is the single most important detail — Swiss apostrophe-separated amounts are the silent killer of homegrown CSV importers.
The cascade
Five layers, and the cheapest one wins.
Layers run in order and stop the moment a column resolves. That is the single biggest cost lever in the system: a column caught on layer 2 never reaches the metered layer 5.
- L1Statisticsno LLM
Auto-accepts a header that past confirmations already resolved the same way, at {minN:100, minRatio:0.95} or {minN:20, minRatio:1.00}.
- L2Heuristicno LLM
Normalises accents, punctuation and whitespace, then compares against the column name, the label, and every registered hint (DE / FR / IT / EN / ES).
- L3Fuzzyno LLM
Token-set ratio plus Levenshtein over the normalised strings. Auto-accepts at 0.80 — it absorbs typos and reordered words.
- L4Semanticcheap, cached
Embedding cosine between the header and the field’s label + hints. Catches the long tail of paraphrases.
- L5LLMmetered
Everything still unresolved goes up in ONE batched, collision-aware call, constrained to this template’s column set so it cannot invent a field.
Try it
One template id, two ways in.
REST for your import pipeline, MCP for your editor. Both run the same cascade and both honour the same schema-only clamp.
REST · POST /v1/uploads
Name the template; the cascade picks up the rest. The canonical definition is read-only at GET /v1/templates/transactions_v1.
curl -X POST https://api.adaptivmapr.com/v1/uploads \
-H "Authorization: Bearer $ADAPTIVMAPR_API_KEY" \
-F "template=transactions_v1" \
-F "file=@your_data.csv"MCP · Cursor / Claude Desktop
Drop AdaptivMapr into your editor and call the same cascade as a tool. Schema-only calls leave only column names and up to three clamped sample rows.
// In Cursor or Claude Desktop with the AdaptivMapr MCP server installed:
adaptivmapr.match_headers({
template_id: "transactions_v1",
headers: ["id", "amount", "currency", "status"]
})Questions
Transactions CSV import — FAQ
Ready when you are
Map transactions in production — without shipping raw records.
Schema-only mode leaves only headers and a handful of clamped samples. Add full-data when you need row-level AI, routed in-region under a BAA.