Get a transaction by ID
Authentication
Bearer token authentication for Mercury API.
Use your API token in the Authorization header:
Authorization: Bearer TOKEN
Example:
Authorization: Bearer secret-token:mercury_production_wma_24SCp4G81X3yHL4Wq8FgzuaP9ye3VKf2mgTDctXyRg5HY_yrucrem
Your Mercury API token should include the ‘secret-token:’ prefix. Tokens can be generated from your Mercury dashboard settings.
Path parameters
Response
List of file attachments (receipts, check images, etc.).
GL code allocations assigned to this transaction via a connected accounting software integration (e.g. QuickBooks, Xero, NetSuite). Each allocation has a GL code name and the amount allocated to it; amounts sum to the transaction total when the transaction is fully categorized. Empty if no GL codes have been assigned. Distinct from Mercury custom categories (see transactionCategoryData).
Whether Mercury has auto-generated a receipt for this transaction.
The type of transaction (e.g., externalTransfer, internalTransfer, cardPayment).
Current status of the transaction (pending, sent, cancelled, failed).
Bank-provided description of the transaction.
Present for check deposits and mailed checks; Nothing otherwise.
User-defined nickname for the counterparty.
Payment method routing details (ACH, wire, check info).
Deprecated: use transactionGlAllocations instead. This field does not reflect GL codes assigned via Mercury auto-categorization rules. Preserved for backwards compatibility.
Mercury-assigned spending category.
Internal note on the transaction (not visible to counterparty).
Human-readable reason for transaction failure, if applicable.
Present for transactions that have tracking numbers (e.g., RTP, ACH, wires); Nothing otherwise.

