Patch docs/spec.md

This commit is contained in:
ai-bot committed 2026-11-14 17:45:31 +00:00
1 parent a17e3c3225
commit 6993f9b0b7
1 file changed
+12 -1
+12 -1
View File
@@ -617,9 +617,20 @@ CSRF header. Errors are `{"error": "<nynorsk message>", "field": "<field name or
`POST`/`PATCH` accept `lot_picks` as a list of `{origin_tx_id, origin_seq, sats}`. Omitted or `POST`/`PATCH` accept `lot_picks` as a list of `{origin_tx_id, origin_seq, sats}`. Omitted or
empty means "use the method". empty means "use the method".
The API takes sats as a whole number: `1500000` or `"1 500 000"`. A decimal number of BTC is
rejected. A NOK amount may carry two decimals, as the storage is øre.
For `admin_cost`, `market_id` must be absent or null, `lot_picks` are rejected, and a fee is
rejected; the account is not required and not looked up.
Every transaction object carries `btc_price_ore`: the bitcoin price of §7.3 in øre per whole
BTC, or null when the type has no price. The lot objects carry the same field name for the same
unit, worked out from the lot's remaining cost and sats.
The CSV export is a plain semicolon-separated file with a UTF-8 BOM so it opens correctly in a The CSV export is a plain semicolon-separated file with a UTF-8 BOM so it opens correctly in a
Norwegian Excel: one block of report rows, then one block of the year's transactions with the Norwegian Excel: one block of report rows, then one block of the year's transactions with the
consumed cost per transaction. consumed cost per transaction and the transaction's bitcoin price. Kroner are written as whole
kroner and BTC quantities as whole sats, the same as the UI.
--- ---