ETA February
API fields deprecation
This is the first deprecation notice of the Morpho API. One can expect this kind of deprecation notice every 6 months. This is a cleanup fields removal, removing only fields that are marked as deprecated for more than 1 year, with an alternative or a non longer maintained feature.
Fields removed & alternatives
Field | Alternative |
| NA |
| |
| NA |
| NA |
| NA |
| NA |
| NA |
| NA |
| |
| |
| |
| NA |
| |
| |
| |
| |
|
|
Changes represented by market(s) / vault(s) are also applied to marketByUniqueKey and vaultByAddress queries.
16/10/2025
Limiting the maximum complexity of a query
Action
GraphQL complexity details:
- Max allowed complexity: 1,000,000
- Base cost per operation: 10
- Each field adds cost; some fields declare explicit costs and/or multipliers.
Troubleshoot
Most queries are unaffected but you can check your queries' complexity in https://api.morpho.org/graphql -> the complexity number is returned as an extension.
If one of you query is above the threshold, you have the following alternatives:
- Trim the selection set: keep only fields you actually use. Prefer cheap snapshots (state.*) over histories when possible.
- Lower fan-out: reduce first (e.g., 25 or 50), then paginate.
- Split the work: fetch a light list first (IDs + a few cheap fields), then run follow-up queries for heavy history on a subset.
- Tune multipliers: for fields like currentIrmCurve(numberOfPoints: N), lower N.
20/09/2025
Search limitation
Rational
The numberOfResults was previously unbounded so the query can yield a huge amount of results which can have an impact on the performance of the Morpho API.
Action
The numberOfResults parameter in the search root resolver (previously unconstrained) will be constrained to be within [0, 1000] (its default value 5 remains unchanged)
Here is an example of search query
19/09/2025
Fields deprecation
Rational
Some rewards fields were wrongly computed since the Merkl integration:
yearlySupplyTokens
yearlyBorrowTokens
amountPerSuppliedToken
amountPerBorrowedToken
Action
These fields will always be set to 0 and be deprecated in the schema.
Troubleshoot
The Morpho API is integrating Merkl, these fields shouldn’t be used and instead supplyApy and borrowApy fields should satisfy integrators needs.
The only deprecated use-cases along with this 4 fields should be:
- displaying rewards for an unpriced asset
- computing the apy with a custom price (fdv feature on the Morpho app)