tracking_history
Show how a SWIFT payment's tracking results changed over time.
Returns the DISTINCT tracking results recorded for a payment (by UETR or reference), deduplicated so ten identical re-tracks collapse to one entry while any change — a new last-update, a status change, or new bank data — appears as its own entry. Each entry includes what was ENTERED when the search was run (amount, currency, date) alongside the banks that reported data and their confirmed amount / value date.
WHEN TO USE THIS:
The user says the page shows different data than you see, or asks why a bank line (e.g. JP Morgan) "disappeared" or a value date differs.
You need to reconcile an amount discrepancy. Correspondent banks such as JP Morgan return their confirmation ONLY when the tracked amount exactly matches the payment, so a search run with the wrong amount silently drops their line. Comparing entries here — same UETR, different entered amounts, different bank data — is how you spot that the amount was the problem.
Before concluding "the record was consolidated" or "the bank stopped reporting", check the history: the earlier result you're being asked about is usually still here, under a different entered amount.
Each bank entry's source names the tracking SOURCE that reported it (e.g.
"Standard Chartered"), not the bank at a step of the payment; track_payment
names the same data by the bank at each step, so the two names differ.
Only results for the current user (plus system tracks with no owner) are returned; other users' searches of the same UETR are never shown.
Requires an API key with an active FI subscription.
Args: uetr: UETR (UUID v4) of the payment. Strongly preferred. reference: Sender's reference (MT103 Field 20) — used when no UETR.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| uetr | No | ||
| api_key | No | ||
| reference | No |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||