Lighter API/MM Updates
1.02K subscribers
1 photo
1 video
78 links
Official Channel for API and Market-maker updates on Lighter
Download Telegram
Currently, only api_key_index:0 and api_key_index:1 are being reserved to serve desktop and mobile users on the lighter front-end

Starting March 22, 2026 at 2:30 PM UTC, the following indexes will be reserved to serve web and mobile users:

- api_key_index:0
- api_key_index:1
- api_key_index:2
- api_key_index:3

If you're currently using indexes 2, 3 for programmatic api trading, you should switch to any other other index in the 4-254 range to avoid any disruption.
πŸ‘4
FYI: We will be updating our WTI methodology to a continuously rolling method in the near future. Starting Monday March 16th, WTI will track 100% CLK6 until further notice, expected in early April. We will keep you updated.
πŸ‘6❀1πŸ‘Ž1
- Volume quota cap has been increased from 5M to 15M
- This change: https://t.me/lighter_api_updates/101 to our WebSocket logic has been postponed to next Monday, March 23rd at 12pm UTC. Testnet already has the new logic, and you can fallback to the old (current) ping/pong logic adding server_pings=true to the WebSocket URL. This fallback will be made available on mainnet too, for a few days after we deploy the changes.

Other changes:
- You can now use the active_only filter on the account endpoint to hide markets for which leverage and margin settings are present (meaning, you traded the market at least once), but with no active position at the time of your request
- The logs endpoint for markets via the explorer api now supports pagination: https://apidocs.lighter.xyz/reference/get_markets-symbol-logs
- Maker trades are now available via the explorer api
❀7
Reminder to stop using {2,3} as api_key_index values, as we'll reserve them starting March 22, 2026 at 2:30 PM UTC. See here for additional details: https://t.me/lighter_api_updates/106

Additionally, you can now query the tokenlist endpoint to fetch categories used to filter available markets on the exchange: https://apidocs.lighter.xyz/reference/tokenlist-1
❀4
The improved WebSocket logic has been deployed to mainnet.

Find all details for the changes here: https://t.me/lighter_api_updates/101

Additionally, for a few days you will be able to fallback to the old ping/pong logic (other changes will still apply) adding this query parameter to the WebSocket URL: server_pings=true
πŸ‘6
Volume quota generation has been improved, now requiring $3 of volume to increase quota by one. Complete details are available here: https://apidocs.lighter.xyz/docs/volume-quota-program
πŸ‘7
Recent updates:

- Clients are now allowed to skip nonces. This is optional, and can be done by setting the SkipNonce field in L2TxAttributes to 1. We still require the next nonce to be higher than the previous, and lower than 2^47-1. SDKs support will be rolled out later this week
- The number of available sub-accounts has been increased from 8 to 64 on the highest staking tier, or fee credits equivalent
- The builder tier is now available, allowing 240K weighted requests on read endpoints, at no extra cost. You can reach out via Discord support channels to be part of the program
- The order_book and ticker WebSocket channels now include last_updated_at, a committer-level microseconds timestamp
- liquidation_price is now correctly displayed on WebSocket channels that return position data
❀8πŸ‘2
- Lighter's GO & Python SDKs have been updated to support skipping nonces. Examples on how to skip nonces, and how to use grouped orders with partner codes have been added: https://github.com/elliottech/lighter-python/tree/main/examples

β€’ total_funding_paid_out has been added to the account endpoint, and the account_all WebSocket channel, allowing to fetch total funding paid out for an existing position without requiring authentication

- We're now able to share an S3 bucket containing all trade events going back to mainnet genesis with interested parties, updated daily. You can reach out via Discord #support to obtain access
❀6πŸ‘2
From now on, clients on a premium account will be able to mark some api keys as maker-only, restricting them to 0ms speed bump transactions only. Those can include:

- Post-only (ALO) orders
- Modify orders on ALO orders
- Cancel, and Cancel All orders

The direct benefit of using this configuration is having access to an optimized execution path, with reduced scheduling latency.

Implementation notes:
- Order types with any type of speed bump sent via a maker-only key will be rejected (error 62007)
- We apply a 1-hour cooldown in between api key type changes (error 62008)
- Maker-only api keys are only accessible by premium account types. Standard accounts will be rejected (error 62009)
- Api key indexes reserved by our front-end cannot be switched to maker-only (0-3)
- A maximum of 200 api keys can be set as maker-only, per account index
- It might take around a second for the api key type change to be effective
- Setting an array of keys as maker-only replaces the previous restrictions. Sending an empty array clears all maker-only restrictions
- To set an api key as maker-only, and get a list of them, we added POST /api/v1/setMakerOnlyApiKeys and GET /api/v1/getMakerOnlyApiKeys (both auth-gated): https://apidocs.lighter.xyz/reference/setmakeronlyapikeys ; https://apidocs.lighter.xyz/reference/getmakeronlyapikeys
❀8
You can now use the partnerStats endpoint to retrieve builder activity stats under the Partner Attribution program: https://apidocs.lighter.xyz/reference/partnerstats.

Additionally, builders managing multiple clients can authenticate each request to bypass IP-based rate limits, so that only L1-based limits apply. The builder tier is not required for this.
❀5
What is live after today's upgrade:

- You can now use Client Order IDs (CID) to group related orders (e.g., TP/SL). This lets you deterministically link them without relying on post-submission data.
- Maximum pending orders increased from 200 to 500.
- Other performance improvements.
❀7
Today, we’re launching the Liquidity Partner Program, designed to reward participants who provide liquidity across RWA markets on Lighter. The program is open to anyone interested in supporting liquidity in these markets.

We are focused on delivering best-in-class liquidity to ensure traders can enter and exit positions in these markets efficiently.

This program is live; the full details are available in our public documentation: https://docs.lighter.xyz/liquidity-partner-program
❀4
Starting Thursday at 12:00 PM UTC, rate-limited requests may return either:

- HTTP 429
- HTTP 405

Currently, only HTTP 429 is returned. Clients should start treating both as indicators that they have been rate limited.

Details about cooldown periods can be found in our docs: https://apidocs.lighter.xyz/docs/rate-limits#cooldown
❀3
Volume quota generation has been improved, now requiring $2 of volume to increase quota by one.

Complete details can be found here: https://apidocs.lighter.xyz/docs/volume-quota-program
πŸ‘4
Reminder: RWA market fees are turning back on at 2:30PM UTC β€” applied based on your tier.
πŸ‘5
- Support for Client Order Indexes on Grouped Orders, and switching between Simple & Unified Margin Mode, has been added to both Python & GO SDKs

- The market_stats WebSocket channel now returns mid_price

- is_taker_fee_enabled and is_maker_fee_enabled fields have been added to the orderBookDetails endpoint, allowing clients to verify markets where fees are disabled. Currently, only $LIT has maker fees set to zero

If you'd like to share feedback on your api experience so far, or request new features, please use this form: https://forms.gle/TYLA6XRYNuPFHvoq8
❀1πŸ‘1
Weekly Liquidity Partner Program Update

- added SPY and Korean Stock USD markets
- introduced Korean market hours support
- expanded listings: ZEC, AAVE, MON, ZRO, XPT
- adjusted weekend bps (wider spreads for oil, metals, and Korean markets)

- Liquidity Partner Program docs: https://docs.lighter.xyz/liquidity-partner-program
- Market Tiers week 2: https://docs.google.com/spreadsheets/d/1JMZMEtdVU6_BAGGrEucHPBxDprbXdbWFq9MkJ-5Jqko/edit?gid=684854736#gid=684854736
❀3
We will be performing a network upgrade on April 24, 2026 at 10:00 AM UTC. Expected downtime is under 20 minutes.

Please manage your positions in advance, as order placement will be unavailable during the upgrade.
πŸ‘4
We’ll be doing a brief ~2 minute restart to apply a configuration fix. We will start this at April 24, 2026 at 11:35 AM UTC, so very soon