Reach out to us if you are using Pendle’s LP Oracle

You can reach us via build-on-pendle channel on Discord. As Pendle becomes more permissionless, certain security assumptions of SY will change in the future, and the Pendle team will verify for all teams currently integrating the LP Oracle that their integration meets the new security assumptions of SY.

New Pendle SDK Feature: Choose which aggregators to use for routing

We're excited to announce a new feature of our hosted SDK, offering:

✅ Allowing you to select aggregators to use for routing

Key Information:

1. Benefits:
- You can now select which aggregators you want to use for routing, giving you more flexibility to choose the best route for your use case.

2. How to use?
- Use version 2 of the supported API, and set the aggregators parameter to the aggregators you want to use! More on it in our documentation for the new feature: https://docs.pendle.finance/pendle-v2/Developers/Backend/HostedSdk#select-aggregators
- A list of endpoints that support this feature can be found in our API swagger, in the SDK section: https://api-v2.pendle.finance/core/docs#/SDK

3. Deprecation of version 1:
- With this new feature, we will deprecate version 1 of the supported API (which does not support selecting aggregators).
- A list of deprecated endpoints can also be found in the swagger above

4. Who will be affected by the deprecation?
- All those who are using our hosted SDK are affected by the deprecation.

5. Deprecation Timeline:
- Version 1 of the supported API will be removed on September 1, 2025.

We're here to support any of your dev needs. Don't hesitate to reach out for any assistance!

New Tool Launch: Pendle Developer Q&A Bot

We’re excited to announce the launch of our new Pendle Developer Q&A Bot, designed to answer your questions about:

✅ API
✅ Contract interactions

Key Information:
- Get instant answers to your dev, API, and smart contract interaction questions.
- Reduce back-and-forth and speed up your development process.
- Available 24/7 to support your integration needs.

How to use?
- Simply open the bot at: https://t.me/peepo_the_engineer_bot
- Ask any question related to Pendle’s APIs, contracts.
- The bot will provide answers, with references to our documentation.

New Pendle SDK Feature: All-in-one convert API

We're excited to announce the new all-in-one convert API for our hosted SDK, offering:

✅ One endpoint for all Pendle interactions with consistent response format

Key Information:

1. Benefits:
- Unified Interface: One /convert endpoint replaces 12+ individual endpoints
- Smart Action Detection: Automatically determines the action (swap, add liquidity, mint PT/YT, etc.) based on inputs and outputs
- Consistent Responses: Unified response structure across all supported actions
- Alternative routes: Get multiple route options for the action

2. How to use?
- Use the new /v2/sdk/{chainId}/convert endpoint, the interactive explorer for this is at https://api-v2.pendle.finance/core/docs#/SDK/SdkController_convert
- Full documentation and examples: https://docs.pendle.finance/Developers/Backend/BackendAndHostedSDK#pendle-hosted-sdk

We're here to support any of your dev needs. Don't hesitate to reach out for any assistance!

Reminder that we will remove SDK version 1 API this week!
Do migrate to version 2 ASAP!

API Update: We’re changing the default behavior from using all supported aggregators to using a preset selection of aggregators. The update will take effect on 06 Nov 2025.

When calling the SDK endpoint with enableAggregator=true without specifying aggregators:

Before: All aggregators were used by default.

Now: A preset set of aggregators will be used, which may change over time for optimization.

If you want to use more aggregators, explicitly set them in the aggregators parameter.

For full details on aggregators and routing behavior, see the documentation:
https://docs.pendle.finance/pendle-v2/Developers/Backend/BackendAndHostedSDK#select-aggregators

New API: Scaled Order Generation
We’ve released a new endpoint that allows you to generate scaled (laddered) limit order data automatically, making it easier to distribute orders across price levels.

Check here for the details: https://api-v2.pendle.finance/core/docs#/Limit%20Orders/LimitOrdersController_generateScaledLimitOrderData

New V6 Factories & Oracle Deployment

We've deployed YieldContractFactoryV6, MarketFactoryV6, and updated oracles (PyLpOracle & Chainlink) with enhanced security. All new Pendle PT, YT, and Markets will use these V6 factories.

For Developers:
- V6 factories are fully backward compatible—no action needed for most integrations
- Old oracles remain functional, but we recommend switching to the new oracle for V6 markets for stronger security

Deployment addresses: https://github.com/pendle-finance/pendle-core-v2/tree/main/deployments

Questions? Feel free to reach out!

Introducing Paid Plans for Higher API Rate Limits

We are introducing paid plan for those who want a higher rate. Free users are not affected (rate limit remains 100 CU per minute, 200k CU quota per week).

# How does API pricing work?
Our pricing is simple and scalable: $10/week = 500 CU/min + 1,000,000 CU/week.

You can purchase multiple units to scale your rate limits based on your application's requirements.

# How to upgrade?
Use our API portal at: https://api-v2.pendle.finance/dashboard/

More information can be found in our documentation: https://docs.pendle.finance/pendle-v2/Developers/Backend/ApiOverview#api-pricing-plans.

Introducing Optional `receiver` Parameter in SDK Endpoints

We have updated our SDK endpoints so that the receiver parameter is now optional.

Validation of Invalid Receivers Begins Soon
Starting 12 Dec 2025, we will begin enforcing validation to reject invalid receiver addresses.
Examples of invalid receivers include:
- The zero address
- Pendle market contract addresses

Please ensure your applications do not submit such addresses to avoid disruptions once validation goes live.

Contract upgrades to support sPendle

We expect none of the upgrades to affect readers as they are mostly at incentive levels. Below are the details:

- VotingController will no longer be used in the Pendle V2 system.
- Gauge controller upgrade:
- Reward data will no longer be updated via the voting controller.
- Reward data will be updated manually on each chain.
- Removed events:
- ReceiveVotingResults(uint128 indexed wTime, address[] markets, uint256[] pendleAmounts);
- UpdateMarketReward(address indexed market, uint256 pendlePerSec, uint256 incentiveEndsAt);
- Added events:
- UpdateMarketRewardV2(address indexed market, uint128 pendlePerSec, uint128 incentiveEndsAt);
- Pendle market and market factory upgrade:
- Pendle markets no longer depend on vePendle.
- Market boosting is removed.
- User rewards are distributed pro rata to their LP balance.
- The legacy activeBalance function is retained and now returns the user’s LP balance.
- Removed events:
- UpdateActiveBalance(address indexed user, uint256 newActiveBalance)
- Markets in this version expose a VERSION function that returns 7.
- Pendle Yield factory and PT/YT contracts are not changed.

## Update: Limit Order Expiry & Incentives

We are updating our expiry requirements to ensure your orders have sufficient time to be filled and to maintain consistency across our platforms.

---

### New Expiry Requirements
* API: Minimum expiry of 5 minutes.
* UI: Minimum expiry of 7 minutes (includes a buffer to prevent premature expiration during processing).

### Incentive Eligibility
To qualify for incentives, an order must meet one of the following:
* Remain active for at least 3 minutes.
* Be at least 50% filled within those first 3 minutes.

### Why the Change?
These updates reduce timing mismatches and provide a more stable window for your orders to find liquidity, ultimately making it easier for your trades to be successfully executed.

# 📣 New: Live order-book stream via Socket.IO

Pendle V2 order-book snapshots are now pushed over Socket.IO every 5 seconds for every whitelisted-pro, safe, non-expired market — no more polling the REST endpoint.

## How to use

1. Connect to https://api-v2.pendle.finance, namespace /pendle-v2.
2. Emit subscribe with room id market:<chainId>-<marketAddress>:order-book:precision-<0|1|2|3> (precision is decimal digits in percent).
3. Listen for order-book events — same payload as GET /limit-order/v2/order-book/:chainId.

## Docs

📖 [Socket.IO Real-time Feeds](https://docs.pendle.finance/pendle-v2-dev/Backend/SocketIO)

Pendle Developer Tools is live ⚡
Need a price feed for a PT or LP token? You used to file a request and wait. Not anymore.

Deploy your own Pendle oracles — permissionlessly, in minutes.

• PT oracles — for fixed-yield positions
• LP oracles — for Pendle liquidity tokens
• Drop straight into lending markets, vaults, structured products, risk engines — anywhere you need reliable
Pendle pricing

No gatekeepers. No tickets. No waiting on the core team.

If you're building on Pendle, this is your new starting line.

👉 dapp-public.pendle.finance