First ask whose role the field describes
A boolean labelled maker can describe a side of a public trade or a role in an account-specific execution. Copy the original field name and the endpoint type before translating it. Similar-looking booleans are not evidence that the same participant is being described.
The cited Spot glossary defines isBuyerMaker in relation to the buyer side. Account trade responses separately show side and maker fields such as isBuyer and isMaker. These examples explain why perspective belongs in the data dictionary; they do not establish a universal flag vocabulary for every venue or product.
Keep the public trade and own fill as separate records
Consider an invented public trade 77 for DEMO-PAIR with isBuyerMaker=true. Under that documented buyer-maker meaning, the buyer supplied liquidity; the corresponding aggressive side is the seller. This still does not tell you whether your account participated.
If a separately saved own fill is validly linked to that trade and says isBuyer=false and isMaker=false, your supplied record describes a selling taker. A linked record with isBuyer=true and isMaker=true would instead describe the passive buyer. Without the account record and a valid join, your role remains unknown.
| Evidence | Proposed interpretation | What it cannot prove |
|---|---|---|
| Public buyer-maker=true | Buyer is the maker under that schema | Your participation |
| Linked own buyer=false, maker=false | Own selling-taker record | Authenticity of the supplied file |
| No valid own-fill link | Personal role unknown | Do not fill the gap from the public flag |
Do not lose the join at Singapore midnight
A fictional fill at 2026-10-22T00:01:00+08:00 belongs to 22 October in a Singapore diary and 21 October at 16:01 UTC. Filtering an exchange export by the wrong calendar date can remove the very account row needed to interpret your role.
Retain the full instant and your stated reporting zone. Then join using the venue, instrument and documented trade/order identifiers at their proper scope. A numeric trade ID should not be treated as globally unique across every instrument, account or export without evidence.
Do not apply one order label to every fill
Two supplied fills associated with one order can carry different role fields. Preserve the role on each linked execution rather than overwriting all rows from the order's display label. The word limit in an order description is not, by itself, the account-level maker evidence needed for every execution.
If one account fill has an explicit maker=true and another has maker=false, report the two entered roles separately. If only an order-level field is available, mark the execution-level role unresolved. You also need a separate decision for corrections and duplicates: counting the same saved execution twice does not establish two maker events. Neither role-count arithmetic nor a public buyer-side flag authenticates the account data.
A role flag is not a fee or profit result
Record the source-specific interpretation next to the raw boolean. Preserve missing values as missing; false means an explicitly supplied false, not a blank cell. If two linked records conflict, retain the conflict and review the join instead of choosing the more convenient side.
Maker/taker classification alone does not supply the commission rate, any rebate, a queue position or profitability. Fee and account evidence would be separate inputs. This worksheet-style reading method does not fetch an account, submit an order or independently authenticate a public or private trade record.
The optional link below leads to this site's separate crypto signals and Telegram updates offer. The record method is usable without that offer. It does not independently verify the offer, establish country eligibility or turn the teaching example into an actual transaction.
Primary sources and scope
- Binance Developer Docs: Spot API glossary
Source-specific meaning of isBuyerMaker; no universal interpretation of every venue flag. Checked 2026-10-21. - Binance Developer Docs: Spot account data
Illustrative account-trade maker/side fields and account records, not authenticated records from a real account. Checked 2026-10-21.