Public API changes - October 2026

🚀 1. Release Notes


[IDM] Updated APIs: Fund legal entity currencies

  • Summary: A fund legal entity can now support several currencies. Create, update and get fund legal entity carry two new fields:

    • currencies: ISO 4217 codes of the currencies the fund legal entity supports, in display order. On create, defaults to [defaultCurrency], or ["USD"] when both fields are omitted. On update, it replaces the whole list.
    • defaultCurrency: the default currency, which must be one of currencies. Required when currencies has more than one value.

    Additive and non-breaking. Existing fund legal entities keep their current currency as their only and default currency.

  • Area of impact: Investor Data Management APIs

  • Released date: November 3, 2026


[IDM] Updated APIs: Investment commitments and balances in multiple currencies

  • Summary: An investment can now hold one commitment and one balance per currency of its fund legal entity. New fields commitments and balances are lists of { amount, currency } objects, where currency is an ISO 4217 code:

    • Responses list the fund legal entity's default currency first, then the other currencies by code.
    • Create: each item must have an amount; without currency, the fund legal entity's default currency is used.
    • Update: omit a list to leave it unchanged; send [] or null to clear it.
    • Import / upsert: omit a list to leave it unchanged; send [] to clear it.
    • Export: new commitments and balances columns hold each list as a JSON array.
    • A currency may appear only once in a list. A supported currency the fund legal entity doesn't have yet is added to it.

    Additive and non-breaking. Existing investments return their current commitment and balance as one-item lists. The single-amount fields commitmentAmount and balanceAmount keep working (see the deprecation below).

  • Area of impact: Investor Data Management APIs

  • Released date: November 3, 2026


[IDM] Updated APIs: Transaction amount with its currency

  • Summary: A transaction's amount now carries its currency. The new field transactionAmount is a { amount, currency } object:

    • Responses return the accepted amount, else the capital amount, else the estimated amount, with its currency. Absent when the transaction has no amount.
    • Create: the object must have an amount; without currency, the fund legal entity's default currency is used.
    • Update: without currency, the transaction keeps its current currency. null removes the amount; omit it to leave the amount unchanged.
    • Import / upsert: an omitted or null transactionAmount leaves the amount unchanged.
    • Export: a new transactionAmount column holds the amount as a JSON object.
    • Sending both transactionAmount and the deprecated amount is rejected.
    • A supported currency the fund legal entity doesn't have yet is added to it. Changing the currency never converts the amount.

    Additive and non-breaking. The amount field keeps working (see the deprecation below).

  • Area of impact: Investor Data Management APIs

  • Released date: November 3, 2026


[FundSub] Updated APIs: Return fund legal entities in fund info

  • Summary: Fund Subscription APIs now show which fund legal entity each sub-fund and order belongs to, so integrations can map Anduin data into systems organized by legal entity (fund admin, accounting, portfolio management).

    • Get fund information: new legalEntities list on the fund (id, customId, name) and new legalEntityId on each sub-fund.
    • Get workflow data for an order / for all orders: new legalEntities list on each order and new legalEntityId on each commitments[].subFund. An order’s list can be empty ([]) when it isn’t assigned to a legal entity yet, and it can change when commitment amounts change.
    • Legal entity IDs here are specific to Fund Subscription and are not the same as the Fund Legal Entity IDs in the Investor Data Management APIs. Map them by customId or name.
    • Fundraise workflows only. Also available in the MCP tools get_fund_info and get_order_workflow_data.

    Additive and non-breaking.

  • Area of impact: FundSub APIs

  • Released date: November 3, 2026


[FundSub] Updated APIs: Comment APIs – Rich text formatting

  • Summary: Comments now support rich text formatting. Import comments and Bulk import comments accept a new bodyHtml field as an alternative to body. In body, lines starting with - or 1. now become lists (start a line with \ to keep it as text). List thread comments and Export fund comments return bodyHtml when called with include=bodyHtml.
  • Area of impact: FundSub APIs
  • Released date: November 10, 2026

[FundSub] New API & Webhook: Order side letter status and files

  • Summary:
    • New API Get order side letter: returns an order's side letter status and the files of its latest version, each with fileId, upload time and uploader. The fileId works with the existing file download API.
    • New webhook fundsub.order.side_letter.status.updated: fires on every side letter status change (oldStatus → newStatus). Payload: fundId, orderId, oldStatus, newStatus, versionNumber, updatedAt.
  • Area of impact: FundSub APIs, New webhook events
  • Released date: November 10, 2026


🛠️ 2. Planned Items


[IDM] Deprecated fields: Investment commitmentAmount and balanceAmount, Transaction amount

  • Summary: The single-amount fields below are deprecated and will be removed on June 1, 2027. They work as before until then.
    • Investment commitmentAmount and balanceAmount: use commitments and balances instead. In a response, they return only the amount in the fund legal entity's current default currency. In a request, they set only that currency's amount and keep the others.
    • Transaction amount: use transactionAmount instead. In a response, it returns only the accepted amount, without its currency. In a request, it uses the fund legal entity's default currency on create, and keeps the transaction's current currency on update.
    • The matching commitmentAmount, balanceAmount and amount columns in the import and export CSV files are deprecated too.
  • Area of impact: Investor Data Management APIs
  • ETA: June 1, 2027