Skip to content

fix(moonpay-export-data): read transaction amounts from amountIn/amountOut - #96

Open
kevarifin14 wants to merge 1 commit into
mainfrom
kevinarifin/export-amount-shape
Open

kevarifin14 wants to merge 1 commit into
mainfrom
kevinarifin/export-amount-shape

Conversation

@kevarifin14

@kevarifin14 kevarifin14 commented Oct 14, 2026 •

Copy link
Copy Markdown
Contributor

MoonPay CLI #649 (https://github.com/moon-labs-dev/moonpay-cli/pull/649) changes transaction_list/transaction_retrieve to report amounts as amountIn/amountOut ({ amount, raw, decimals, symbol, usd }), replacing from.token, from.amount, to.token, to.amount and the top-level usd. Without this change, the transaction CSV export produces blank token, amount and USD columns.

  • The transaction history jq now reads .amountIn.symbol, .amountIn.amount, .amountOut.symbol, .amountOut.amount and .amountIn.usd. A null leg (for example, a bridge still in flight) exports as empty cells.
  • The first CSV column is labelled transaction_id, which is what it contains (previously date).
  • Portfolio exports keep reading .balance.value, which #649 doesn't change.

The file now matches packages/cli/skills/moonpay-export-data/SKILL.md in moonpay-cli.

Merge when CLI #649 is deployed. Before then, the current paths are still correct.

…ntOut

Matches moonpay-cli #649, where transaction_list reports amounts as amountIn and
amountOut instead of from/to token, amount and a top-level usd. Balance exports
are unchanged.
@kevarifin14
kevarifin14 marked this pull request as ready for review October 14, 2026 15:48
@kevarifin14
kevarifin14 requested a review from a team as a code owner October 14, 2026 15:48
@kevarifin14

Copy link
Copy Markdown
Contributor Author

Ready to merge now: moonpay-cli #649 is merged and deployed to production (agents.moonpay.com now returns amountIn/amountOut with decimals), so this export jq should land quickly to keep the published skill in sync. It was verified against the new response shape, including null legs, in the #649 review.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant