PR

RPI liquidity now available to API Taker orders

Web3Instant
Web3Instant
Monday, May 25, 2026•3 min read
27,653
RPI liquidity now available to API Taker orders

RPI liquidity now available to API Taker orders

Bybit • Latest Bybit News

Tags: Institutions

Bybit is extending Retail Price Improvement (RPI) liquidity access to API clients across Spot and Derivatives markets, including Linear and Inverse Perpetuals, through an optional opt-in setting.
For systematic and institutional API clients, this update provides:

  • Access deeper, tighter liquidity
  • RPI Maker liquidity typically offers narrower spreads and larger resting size than the standard order book. API orders with rpiTakerAccess=true enabled can now access this liquidity.
  • This is especially beneficial for IOC and FOK executions that previously consumed only visible top-of-book liquidity.
  • Improve execution quality without changing existing API flow
  • At the same price level, the standard API Pool is matched first. The RPI Pool is accessed only when it offers a better price or when remaining quantity is available after the API Pool at that price level is exhausted.

Existing institutional market-making flow remains unchanged.


Backward-compatible by default
Existing API integrations remain unchanged by default because rpiTakerAccess=false is applied automatically.
No code changes are required unless clients choose to opt in.


Effective time
June 12, 2026, 10AM UTC

Scope at launch

  • Spot: RPI-enabled spot pairs
  • Derivatives: Linear Perpetuals (USDT and USDC quoted) and Inverse Perpetuals

A single opt-in parameter enables access across all supported products. You do not need separate integrations for each product line.


Eligibility for matching RPI Maker liquidity
Before this update, RPI Maker liquidity could match only non-algorithmic taker flow. OpenAPI orders could not access RPI liquidity.
With this update, OpenAPI orders with rpiTakerAccess=true enabled can now match against RPI Maker liquidity.

Taker source Before After
App / Web (non-algorithmic) Eligible Eligible
OpenAPI (default) Not eligible Not eligible
OpenAPI with rpiTakerAccess=true Not available Eligible, with 50ms execution delay

Key Updates

App / Web OpenAPI (default) OpenAPI with rpiTakerAccess=true
Speed Bump None None 50ms
Matching pool RPI Pool + API Pool API Pool only RPI Pool + API Pool
Matching priority Best price first → API Pool first at same price → time Best price first → time (within API Pool) Best price first → API Pool first at same price → time
Eligible order types All supported types All supported types Market orders
Eligible products All RPI-listed products All products Spot and Derivatives (Linear and Inverse Perpetuals)
Cancellations Not delayed Not delayed Not delayed

Additional notes
The rpiTakerAccess parameter is configured per order and defaults to false. Existing API integrations remain unchanged unless the parameter is explicitly enabled.
OMS pipelines that default to timeInForce=GTC remain compatible. Bybit automatically converts Market GTC orders into Market IOC orders during submission, so no integration changes are required to opt in.
In the rare event of a trading engine restart, orders still within the 50 ms delay window may not reach the matching engine. Monitor order acknowledgements to confirm successful acceptance.
For full parameter specifications, request examples, error codes, matching priority, and operational considerations, refer to the documentation below.

About RPI orders
RPI orders provide price improvement and differentiated matching behavior for qualified Market Makers.


Key features

  • Exclusive matching: Primarily designed to interact with non-algorithmic flow. API taker access is now available through an opt-in setting with speed bump protection.
  • Post-only: Always adds liquidity to the order book as a maker order.
  • Lower execution priority: Executes after non-RPI orders at the same price level.
  • Restricted access: Available only to qualified Market Makers.
  • GUI visibility: Visible on the trading interface but excluded from API order book feeds.

Documentation
For full parameter specifications, request examples, error codes, and operational details, refer to:

API Documentation
Help Center: RPI Order Overview

Source: Bybit Official Announcement — originally published on Mon, 25 May 2026 00:00:00 GMT.

Ask AI about this article

Powered by Groq

Share this article