Changelog
What changed in the API and the MCP server, newest first.
29 October 2026: a bill stays in its own currency#
convert_toleft out now keeps a bill in the currency it was added in. It used to default to the group's currency, so a bill in another currency added through the API oradd_expensecame back withneeds_fx_rate: trueuntil somebody agreed a rate. Sendconvert_to(the group's currency) to convert on purpose; anfx_ratesent withoutconvert_tois still into the group's currency (Currencies).convert_tois in the REST reference for creating and editing a bill.
8 October 2026: bills by item#
add_expensetakesitemsandextras: each line with who had it, and tax, tip, fees and discounts as an amount or a percent.amountmay be left out, since the lines decide the total (MCP server).- The REST reference documents
itemsandpoolson creating, editing and reading a bill. A pool statesamount_minororrate_bp. A rate is worked out on the items plus every pool before it, so the order is part of the bill. - Reading a bill returns
rate_bpon a percentage pool. It used to be left out, so the pool read as zero. - Nothing is charged on a tip. A
TIPpool no longer counts toward the base of a percentage after it, so "tip, then 5% tax" taxes the items and fees alone.
v1, 28 September 2026: first public release#
- Developer keys: one per account, made in the app under Me › Profile › Developer, with the scope
readorreadandwrite. Keys can be switched off and on, regenerated or deleted from the app, and every request a key makes is logged for its owner (Authentication). - The REST API: 40 operations (24 reads, 16 writes) across groups, bills, comments, balances, payments, repeats, captures, activity, insights and rates (API reference).
- The MCP server at
POST /mcp: 14 tools over Streamable HTTP, protocol2025-06-18(MCP server). - The contract as OpenAPI 3.1 at
GET /v1/openapi.json, the same file this site's reference is built from. - Rate limits: 2 requests a second per key with a burst of 30 (Rate limits).
- This site, with the console for trying calls in the browser.
Compatibility#
Within v1, new fields, new optional parameters, new operations and new error codes can appear. Write clients that ignore fields they do not know and that handle an unknown error code by its HTTP status. Changes are listed here.