0x38c44c3838c4…38c44c35
Morpho Launches REST Read APIs, Sets Early 2027 GraphQL Deadline
Morpho has opened its REST read layer and set an early 2027 GraphQL cutoff, while transaction-building and fee APIs remain slated to arrive later for developers.

Outputs
Morpho’s announcement was dated November 18, 2026.
Read APIs are live, while Action APIs and Monetize tools remain “coming soon.”
Morpho will end GraphQL support in early 2027.
Morpho’s reported 2026 deposits exceeded $14 billion.
The protocol operates on Ethereum and OKX’s X Layer.
DeFi protocol Morpho launched REST APIs for reading protocol data in an announcement dated November 18, 2026; its release materials put total deposits above $14 billion in 2026. The transaction-building and fee tools remain “coming soon,” making this a read-first release.
The three-part platform
Morpho’s refreshed Developer Platform divides into three functions:
- Read: Live REST endpoints provide cursor pagination, filters, historical APY data and protocol-state data.
- Action: Future transaction-construction calls for Morpho’s core protocols will use API-key protection and return “unsigned or simulated transactions.”
- Monetize: Future tools will let integrators attach fees to supported user flows and earn revenue when an application routes activity to Morpho.
Read now runs in production. Action and Monetize have no release dates, so integrators cannot yet rely on Morpho for transaction execution or revenue collection through the platform.
An application can request yield history and protocol positions through ordinary HTTP requests. Before this release, developers might have needed a custom indexer or direct interaction with Morpho smart contracts to assemble the same information. Morpho says Read reduces that infrastructure burden without requiring integrators to handle contract calls for those data products.
The distinction matters because the live release does not automate signing or execution. It supplies information that applications can display, compare and route into product interfaces; users still decide what they approve in their wallets.
What does this change for developers?
Action will construct transactions for Morpho’s core protocols. Calls will sit behind API keys and return unsigned or simulated transactions. The application receives prepared transaction data, while the user reviews and signs it in a wallet. This division keeps custody outside the integration layer and preserves user control over every signature.
Monetize will add built-in fee options for supported flows. A wallet or fintech application that sends users into Morpho could attach a fee and retain it rather than build a separate revenue mechanism. Morpho says integrators will be able to verify transactions, while the protocol does not custody assets or hold user keys.
The practical effect is lower integration cost. A consumer-app team can avoid hiring a Solidity specialist and running a dedicated indexer merely to display a yield figure, according to Morpho’s stated goal. Integration friction, rather than contract design, can become the bottleneck when a protocol distributes through exchanges and fintech applications.
The separation also addresses partner concerns about custody, regulatory exposure and security liability. It does not eliminate operational dependence on an API intermediary, however. Any application connected through Read, Action or Monetize must still manage endpoint reliability, data validation and transaction verification.
The early 2027 migration deadline
Morpho will end GraphQL support in early 2027 and standardize its developer platform on REST. GraphQL allows developers to request specific fields through a flexible query language, but many web developers have little experience with it. REST uses plain HTTP requests, a more familiar interface for consumer-application teams.
Integrators currently using Morpho’s GraphQL endpoints must migrate their queries and clients before the cutoff. The release materials do not specify a final day within early 2027, so teams cannot treat the date as a precise deadline. The retirement nevertheless creates a concrete engineering requirement for any application that still depends on the older interface.
Distribution and deposit scale
Morpho has expanded across Ethereum and OKX’s X Layer, while its release materials describe work alongside consumer platforms including Coinbase and Robinhood. Those channels reportedly attracted substantial deposits, particularly in USDC. The reported total above $14 billion represents Morpho’s 2026 deposit base, although the source provides no monthly or daily breakdown and does not assign a figure to each partner.
The new platform is intended to convert that distribution into developer adoption. By reducing indexing and contract-interaction requirements, Morpho seeks to become infrastructure for wallets and fintech products rather than require each partner to build a separate data layer.
The next execution test
Three milestones will determine whether the platform can support production applications:
- Release Action and Monetize, turning read-only dashboards into transaction-bearing and fee-generating products.
- Migrate existing GraphQL users before the early 2027 cutoff.
- Introduce new integrations on expanding networks, including X Layer.
The first binding checkpoint is the GraphQL retirement, while the commercial test rests on shipping the two pending API layers. A standardized REST interface can widen Morpho’s distribution, but only after the protocol closes the gap between data access and transaction execution.
via Crypto Briefing (Source)
More from Nathan Brooks
Show full bio
Market editor covering money, funding and market shifts around crypto and web3 industry at Mempool Brief.
1,512 articles