🔧 LavaOS API Update - Split Position Endpoint
Split any leveraged position into two separate positions at any ratio, enabling partial position management and advanced trading strategies.

🔗 Technical docs

If you have any questions, or need any explanation about this update, please contact the Lavarage team in your dedicated group chat.

Ready to integrate LavaOS on your platform? Apply for the LavaOS API key:
👉 https://forms.gle/KRTWES9GVfrLcdFd6

GM, we are experience a temporary outage with some of the API endpoints. We are working on restoring them. Sorry for any inconvenience 🙇‍♂️

LavaOS is back online

🔧 LavaOS API Update
You can now filter your position queries by creation date (i.e. openTimestamp) to retrieve positions from specific time periods.

Find the full details here: https://triangular-mail-c77.notion.site/Time-based-Filtering-242d4b2f0d4f80c2a6c1d34957cf03c5

If you have any questions, or need any explanation about this update, please contact the Lavarage team in your dedicated group chat.

Ready to integrate LavaOS on your platform? Apply for the LavaOS API key:
👉 https://forms.gle/KRTWES9GVfrLcdFd6

LavaOS Update - New Endpoint for Multiple Transactions

We've added a new endpoint for handling scenarios where a single transaction doesn't have enough accounts to complete the operation.

This resolves issues where positions fail to open due to transaction account limitations.

When to use:
If you receive a quote failure due to account limits in a single transaction, you can use the multiple transaction endpoint to re-try.

Required parameters:
- splitTransaction: true
- useAstra: true
- Use the rpc-astra endpoint

Documentation:
Full integration details are available here: https://www.notion.so/INTEGRATION-2c8d4b2f0d4f80d981a8d978affbbbe3

If you have any questions or need explanation about this update, please reach out to the Lavarage team.

LavaOS Update – New Regional Endpoint (Southeast Asia)
We've added a dedicated regional endpoint hosted in Jakarta, Indonesia to improve connection reliability and reduce latency for users and servers in the Asia-Pacific region, especially in Southeast Asia.

New endpoint:

https://jakarta.lavarave.wtf/api/sdk/v1.0

Default (global):

https://lavarave.wtf/api/sdk/v1.0

When to use the regional endpoint:
- Your server or users are located in Southeast Asia, East Asia (Hong Kong, Korea, Japan, etc.), or nearby regions
- You're using location-aware edge infrastructure (Cloudflare Workers, Vercel, Netlify) and want to route APAC traffic to a closer node
- You're experiencing intermittent latency spikes or unstable response times on the default endpoint – try the regional endpoint to see if it resolves the issue

No SDK changes required – just swap the base URL. Full details in the API Base Configuration section: LavaOS Integration Guide

Questions? Reach out to us anytime.