0x0c5e68c20c5e…0c5e68c5

ConfirmedInfrastructure591 vB178 sat/vB3 min decode

Morpho Sets Jan. 29, 2027 Deadline to End Its GraphQL API

Morpho will close its GraphQL API on Jan. 29, 2027. Developers must migrate protocol-data requests to key-free REST routes, while the separate Action API still requires a key.

Morpho Sets Jan. 29, 2027, Deadline to End Its GraphQL API
WitnessMorpho Sets Jan. 29, 2027, Deadline to End Its GraphQL APIJESHOOTS-com / pixabay

Outputs

  1. Jan. 29, 2027 is the deadline for Morpho to close its GraphQL API.

  2. Nov. 26, 2025 is when Morpho introduced GraphQL as a read-only interface.

  3. Public REST endpoints use GET requests and require no API key.

  4. The separate Action API requires a key and returns transaction calls without submitting transactions.

  5. Circle’s Arc Earn Kit integrates Morpho vaults and supports ETH- and BTC-backed lending markets.

According to Morpho, the company will close its GraphQL API on Jan. 29, 2027, requiring developers who use it for protocol data to move their requests to REST routes before the service shuts down.

Morpho’s instruction is explicit: “Developers must move protocol data requests to REST routes before the cutoff.” The deadline applies to the GraphQL interface, while Morpho’s separate Action API remains part of the protocol’s current developer offering for transaction-call construction.

What changes on Jan. 29, 2027?

Morpho introduced its GraphQL interface as a read-only service on Nov. 26, 2025. After the shutdown, developers needing protocol information must use its public REST endpoints for market data, vault data and other protocol information. Those endpoints accept GET requests and do not require an API key.

That makes REST the key-free path for public reads after the cutoff. It does not replace every function in Morpho’s developer stack.

The separate Action API requires a key and returns transaction calls for a user’s wallet to approve and send. Morpho says: “The API does not submit those transactions.” Wallet approval and submission therefore remain outside the API’s execution function.

What does the GraphQL-to-REST migration require?

Morpho’s description makes clear that GraphQL and REST do not present the same request pattern. GraphQL packages a data query into one POST, while REST divides retrieval into route-specific GET calls, each with a set response format.

For an integration built around GraphQL, that is an architectural change rather than a simple URL swap. Request orchestration, endpoint mapping and response handling must align with route-specific calls before the cutoff.

Teams using GraphQL for market, vault or other protocol information will need to test those route-level changes before Jan. 29, 2027. The public read migration does not introduce an API-key requirement.

A separate requirement remains for developers that construct transaction calls: they must configure and use a key for the Action API. The API then returns calls for the user’s wallet to approve and send, rather than submitting transactions itself.

Which integrations face the deadline?

The shutdown covers developers using GraphQL to request protocol data. Morpho’s REST endpoints cover that read function through GET requests without a key. The Action API covers transaction-call construction, requires a key and returns calls that a user’s wallet can approve and send; it does not submit the transaction itself.

The split makes the REST migration and Action API configuration separate requirements, not one replacement workflow. A developer can complete the read-data transition without adding credentials to public endpoints, but a transaction-building integration still needs the keyed service and wallet participation.

The wallet, rather than the API, approves and sends the transaction. That boundary leaves users responsible for the final transaction action even after an integration has prepared the requested call through the Action API.

Does the API change affect Circle’s Arc Earn Kit?

Morpho vaults are also integrated into Circle’s Arc Earn Kit. The kit supports lending markets backed by Ether (ETH) and Bitcoin (BTC) collateral. Morpho’s API retirement timetable does not set a separate shutdown date for that Circle integration; its stated deadline remains the migration of GraphQL-based protocol-data requests by Jan. 29, 2027.

Jan. 29, 2027 is the operative cutoff: after that date, GraphQL access ends, public data retrieval runs through key-free REST GET routes, and transaction-call integrations remain dependent on the separate Action API, its key and the user’s wallet.

via tokenpost.com (Source)

More from Daniel Okafor

Daniel Okafor

Show full bio

Correspondent covering people, launches and day-to-day practice in crypto and web3 industry at Mempool Brief.

1,514 articles