Changelog

Added

Events API now available

The new Events API provides visibility into changes to your Mercury resources through a pull-based event log. Query and replay historical changes to your transactions for backfills, reconciliation, and audit trails. The API uses a pull-based model where you query for events on-demand. This enables reliable event replay and backfill scenarios. The API currently supports the Transaction resource type. Additional resource types (Accounts, Cards, etc.) will be added in future updates. If you're interested in events for other resource types, please reach out to [email protected].

Added

Invoicing API now available

The new Invoicing API simplifies managing invoices and customers by allowing seamless integration with Mercury invoicing into your existing systems. Note that it's only available to Mercury users on a subscription plan. Visit https://mercury.com/pricing to upgrade!

Tracking Number now available on Transaction response

All Transaction responses now return an optional trackingNumber: A unique identifier assigned by payment networks to trace transactions (e.g., RTP reference ID, ACH trace number, wire IMAD/OMAD). The field will be null if nonexistent.

New details for Treasury transactions

We added a new detials object for each transaction to the response of the /treasury/:id/transactions endpoint. This new value includes the already existing security but also adds additional details like the id of the account for deposits and withdrawals, descriptions for several actions and trade and sweep directionality details.

Added

Transactions API now avaliable

The /api/v1/transactions API serves as a top level list view for all transactions within your Mercury organization. List, filter, paginate, and search transactions from all your Mercury accounts in a single endpoint. See the documentation here.