binance_get_fiat_orders
List fiat deposit or withdrawal orders (bank transfers, card top-ups) within a specific time window to reconcile individual transactions. Use for targeted lookups, not bulk backfills.
Instructions
List fiat-rail deposit or withdraw orders (bank transfer/card top-up of the fiat wallet).
Calls GET /sapi/v1/fiat/orders, signed. This is the UID-weighted 45000 fiat-rail
ledger — of the 180000/min UID budget that is at most 4 calls per minute. Do not
poll this tool in a loop; for a bulk backfill use binance_get_fiat_history, which
already budgets calls.
When to Use:
Seeing fiat bank-rail deposits into, or withdrawals out of, the fiat wallet (bank transfer, SEPA, card-funded top-ups of the fiat balance — not Spot).
Reconciling a specific order by scanning a narrow begin_time/end_time window.
When NOT to Use:
Buying/selling crypto with fiat (a card or bank purchase of BTC/ETH/...) — use
binance_get_fiat_payments.A long backfill across many pages or months — use
binance_get_fiat_history.Binance Card spend — there is no API for that (see the module docstring).
Returns:
A markdown list (or JSON with response_format="json") of orders: order number,
fiat currency, indicated vs settled amount, fee, method, status, created/updated
time. Status values Binance returns: Processing, Failed, Successful, Finished,
Refunding, Refunded, Refund Failed, Order Partial credit Stopped.
Pagination:
page (1-indexed) / rows (max 500) map directly to the API; the response also
reports Binance's own total row count across all pages. Markdown display is
capped at 50 rows (with a note naming the next page to request); JSON keeps
the full page.
Examples: params = {"transaction_type": "deposit", "rows": 50} params = {"transaction_type": "withdraw", "begin_time": "2026-01-01", "end_time": "2026-02-01"}
Error Handling:
A 200 body with success: false is raised by the client as BinanceEnvelopeError
and surfaced here as Error: ...; an undocumented span cap on this endpoint
typically surfaces as -1127 — narrow begin_time/end_time and retry. A malformed
begin_time/end_time returns Error: <field> must be epoch milliseconds or an ISO-8601 string without calling the API.
Input Schema
| Name | Required | Description | Default |
|---|---|---|---|
| params | Yes |
Output Schema
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |