Changelog
Back to All

Public API changes - September 2026

8 days ago

🚀 1. Release Notes

[IDM] Updated API: List Firm Members – Client Groups & Fund Subscription Access

  • Summary: List firm members now returns two new opt-in objects — clientGroupsAccess (gated by includeClientGroupsAccess) and fundSubAccess (gated by includeFundSubAccess) — each a {data, hasMore} object capped at 20 entries, ordered alphabetically by name, and always present (empty) when not requested. fundSubAccess replaces the existing fundAccess array, which is now deprecated and will be removed on 27 October 2026; until then both are returned and describe the same data. Additive and non-breaking on release.
  • Area of impact: Investor Data Management APIs
  • Released date: September 22, 2026

[IDM] New APIs: List a firm member's client groups & fund subscription access

  • Summary: Two new endpoints retrieve a single firm member's access in full (cursor-paginated), complementing the 20-entry caps on List firm members. Each returns {data: [{ id, name }], total} and responds 404 when the user is not a member of the firm (distinct from an empty list). The fund-subscription endpoint is the supported way to enumerate more than 20 subscriptions once fundAccess is removed on 27 October 2026.
  • Area of impact: Investor Data Management APIs
  • Released date: September 22, 2026

[IDM] Updated Webhooks: Emit an event for every object & relationship removed by a delete

  • Summary: Delete operations now emit a webhook event for every object and every relationship removed by the action, not only the object named in the request. Deleting a Client, for example, now also emits events for each Investment Entity deleted beneath it (and everything beneath those) and for removed relationships — contact assignments, communication matrix entries, portal access, and order links. This introduces relationship-removal events that did not previously exist. Applies to Delete client, Delete investment entity, Delete investment, Bulk delete transactions, and Delete contact. Event order is not guaranteed.

  • Area of impact: Investor Data Management APIs — IDM webhook

  • Released date: September 29, 2026

[Dataroom] Update Export Activity API’s CSV output

  • Summary: Add participant tag column, date column, time column and user group column to the Exported CSV in Export Activity API

  • Area of impact: Data Room APIs

  • Released date: September 29, 2026

[FundSub] Webhook event for Supporting Doc Extraction Status Changed

  • Summary: Introduce new webhook that fires when the OCR extraction status of a supporting-doc extract request changes

  • Area of impact: FundSub APIs

  • Released date: September 8, 2026

[FundSub] Updated API : Get extraction data of an Order: include OCR supporting form data

  • Summary: Extend the "Get extraction data of an Order" JSON API so its response also includes extracted data from OCR supporting forms, not just the main form.

  • Area of impact: FundSub APIs

  • Released date: September 8, 2026

[FundSub] Updated API : Get form data for multiple orders

  • Summary: Return close_date in the Get workflow data for an order API response when the Close field is included in a custom template.

  • Area of impact: FundSub APIs

  • Released date: September 8, 2026

🛠️ 2. Planned Items

[IDM] Deprecated API: Get investment entity document

  • Summary: The Get investment entity document API is deprecated and will be removed after March 30, 2027. Please use Get document instead.
  • Area of impact: Investor Data Management APIs
  • ETA: March 30, 2027

[FundSub] Updated API: Get order supporting doc – documents marked as provided

  • Summary: Each supporting document now returns a markedAsProvided flag, which is true when a fund manager has marked the document as provided outside Anduin. Together with submitted and markedAsNa, integrations can now tell when every document requirement is fulfilled. The flag is also available in GraphQL as SupportingDocument.markedAsProvided on Order.supportingDocs. The existing order-level amlKycDocsProvidedOffline field is unchanged. Additive and non-breaking.
  • Area of impact: FundSub APIs
  • ETA: October 6, 2026

[FundSub] Updated APIs & Webhook: Link each supplemental form instance to its files with formSubmissionId

  • Summary: An investor can fill several instances of the same supplemental form (for example, two W-8BEN-E forms). Each instance now has a formSubmissionId, which stays the same when the form is resubmitted and is the same ID the Order Supporting Form Status Updated webhook already sends. Use it to match each instance's form data to its files:

    • Get form data for multiple orders: every supplementalFormData and templatedSupplementalFormData entry includes formSubmissionId.
    • Get order supporting doc: files produced by a supplemental form include formSubmissionId and formFileRole (formDocument for the filled or signed form, signingCertificate for the e-signature certificate). Both fields are absent on files uploaded without a form.
    • Webhook fundsub.order.supporting_form.status.updated: now includes fileIds and certificateFileIds, which list the form's files when the event fires (an empty array when there are none).

    Additive and non-breaking.

  • Area of impact: FundSub APIs

  • ETA: October 6, 2026

[FundSub] Updated GraphQL: FundSubscription.templates returns all fund templates

  • Summary: FundSubscription.templates now returns the same templates as the REST Get fund info API: fund-manager custom export templates (Excel and API) and Standard Alias (CSA) data templates, alongside the import/export mapping templates it already returned. The TemplateType enum has two new values, SELF_SERVICE_EXPORT (REST SELF-SERVICE-EXPORT) and ORDER_SUBMISSION_EXPORT (REST ORDER-SUBMISSION-EXPORT), and first / offset now paginate across all templates. Integrations that handle TemplateType exhaustively should add the two new values.
  • Area of impact: FundSub GraphQL API
  • ETA: October 6, 2026

[FundSub] New Webhooks: Fund name, custom ID and metadata updated

  • Summary: Introduce three new webhook events, one for each fund field, so integrations can keep fund information in sync. An event fires only when the value actually changes.
    • fundsub.fund.name.updated: the fund is renamed. Payload: fundId, oldName, newName.
    • fundsub.fund.custom_id.updated: the fund's custom ID changes. Payload: fundId, fundName, oldCustomId, newCustomId.
    • fundsub.fund.metadata.updated: fund metadata is updated through the public API. Payload: fundId, fundName, oldMetadata, newMetadata (full metadata before and after).
  • Area of impact: New webhook events
  • ETA: October 6, 2026