Developer release notes Q3 / 2025
The Q3 2025 release features API enhancements, stricter GraphQL conventions, new tool for data exploration, and Jsreport maintenance update.
API changes
New fields via API
The following new fields that we introduced in the Q3 release are also available for GraphQL queries:
paymentAccrualCalendar – Payment calendar (day count convention) (security)
redemptionYieldPeriodicity – Redemption yield periodicity (security)
tradeIncrement – Trade increment (security)
deceased – Deceased (contact)
deceasedDate – Date of death (contact)
We also added support for finding transactions and trade orders based on their effective transaction date. The effective date refers to the transaction’s/order’s booked date if it has one, or the transaction date if it doesn't.
Blocking GraphQL requests using HTTP GET
Before, it was possible to call our GraphQL APIs using HTTP GET or HTTP POST. The established convention is to only use HTTP POST, because this allows passing the GraphQL query/mutation content in the body of the request. To avoid issues in certain edge cases, and to unify GraphQL API usage across our environments, we decided to block GET requests to our GraphQL endpoints, starting from this release. Our statistics indicate this should not affect any of our production customers, but it is something you should be aware of when building or maintaining integrations against our GraphQL APIs.
New APIs for upcoming features
Ongoing development related to FA Invest and CGT calculations have produced several new APIs in FA Back. These APIs are related to CGT calculation and trade simulation. These APIs are highly subject to change, and we do not recommend using them in critical integrations until the corresponding features have been officially released.
New data explorer section in FA Developer
A new Data explorer section in FA Developer app provides a safe sandbox to browse, export, and query the data in your document database. CosmosDB is our document database of choice. It is analogous to MongoDB and can be queried with MongoDB query syntax.
In addition to the new section in FA Developer, you can run queries against your document database via API call.
The new Data explorer section in FA Developer is similar to the Queries view in FA Back. It allows you to flexibly access and explore your data and serves as a diagnostic and administrative tool for FA employees. FA Back’s queries view is more powerful, as the vast majority of FA data is stored in an SQL database, but you can also find uses for the document database explorer when building certain custom integrations or reports, for example.
The same limitations apply to both our queries view and our document database explorer: although we generally try to avoid changing our database schema in backwards incompatible ways, this does occasionally happen. Integrations built based on custom queries are therefore more likely to require adjustments from time to time, than integrations done via our standard GraphQL APIs that are not based on custom queries.
Jsreport version upgrade
In this release, we updated Jsreport from 4.8.0 to 4.10.0 as part of routine version maintenance. Jsreport release notes are available in jsreport GitHub repository. Significantly, the new Chromium version, which is used to render PDF reports, may change layouts of some reports. It is therefore important to test custom jsreport templates to ensure proper content alignment.