Morpho unveils new Developer Platform with REST APIs for integration
Morpho logo, official brand asset
The DeFi protocol's read APIs are live now, with transaction-building and fee tools for integrators coming soon
Morpho wants building on its protocol to feel less like archaeology and more like ordering takeout. The DeFi project has rolled out a refreshed Developer Platform, and its first piece, a set of REST APIs for reading Morpho data, is live today.
Two more pieces are on the way. Action APIs for constructing transactions and Monetize tools that let integrators charge fees are both labeled “coming soon,” so for now this is one course of a three-course meal.
What Morpho actually shipped
The platform is organized into three buckets, each named after what a developer would want to do.
Read covers fetching data from Morpho through REST endpoints. According to research on the release, these include cursor pagination, filters, and endpoints for historical APY and state data.
Translated for non-engineers: an app can now pull yield history and protocol positions with standard web requests. Before, that work might have meant running a custom indexer or wrestling directly with smart contracts.
Action will handle building transactions for Morpho’s core protocols. The research indicates these calls will sit behind API-key protection and return unsigned or simulated transactions.
That design choice matters. The API hands an app a pre-assembled transaction, but the user still has to look at it and sign it themselves.
Monetize will give integrators built-in options to attach fees to supported flows. If a wallet or fintech app routes users into Morpho, it gets a way to earn something for the trouble.
Morpho says integrators will be able to verify transactions, and users will remain in control of everything they sign. The research adds that Morpho does not custody assets or hold user keys.
The crypto and markets news you actually need—every morning.
Daily. Free. Join 34,000+ readers across crypto, finance, and policy.
The quiet retirement of GraphQL
The less flashy part of the update may be the more consequential one for existing builders. Per the research findings, Morpho’s GraphQL support is set to end in early 2027, with the platform moving to REST standards.
GraphQL is a flexible query language that lets developers ask for exactly the data they want. It is also something a lot of web developers have never touched. REST, by contrast, runs on plain HTTP requests, the lingua franca of the internet.
Teams currently relying on Morpho’s GraphQL endpoints have a migration on their calendar. Early 2027 is not tomorrow, but engineering roadmaps fill up faster than anyone admits.
Background: a protocol courting the mainstream
The announcement was dated November 18, 2026, according to the research. It lands as Morpho pushes its footprint across multiple chains, including Ethereum and OKX’s X Layer.
The protocol has also been lining up alongside large consumer platforms, with the research pointing to Coinbase and Robinhood. Those relationships have reportedly brought in substantial deposits, especially in USDC.
The headline growth figure: total deposits exceeded $14 billion in 2026, per the research findings.
The stated aim of the new platform is to let developers launch products on Morpho without maintaining their own indexing infrastructure or handling complex contract interactions by hand.
What this means for builders, users and the DeFi market
The strategy here is fairly legible. When a protocol’s growth increasingly comes from fintech apps and exchanges, the bottleneck stops being smart contract design. It becomes integration friction.
A consumer app team does not want to hire a Solidity specialist and run an indexer just to show users a yield number. A REST endpoint with documentation removes a meaningful chunk of that work, which lowers the cost of saying yes to Morpho.
The non-custodial framing is doing real work too. Action APIs that return unsigned transactions keep Morpho out of the business of holding user funds. For partners worried about regulatory exposure or security liabilities, that separation is a feature rather than a footnote.
There is a trade-off worth noting. Any API layer introduces a point of reliance between apps and the protocol. Morpho’s emphasis on letting integrators verify transactions, and on users signing everything themselves, appears designed to address precisely that concern.
What to watch next is straightforward. First, the actual release of the Action and Monetize APIs, since those are the components that turn read-only dashboards into real products. Second, how smoothly existing GraphQL users migrate ahead of the early 2027 cutoff.
Third, whether new integrations show up on the chains Morpho has been expanding into, including X Layer. The $14 billion deposit figure gives Morpho a sizable base to try to grow from.
Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.

