Skip to main content

Set MMP

info

What is MMP?

Market Maker Protection (MMP) is an automated mechanism designed to protect market makers (MM) against liquidity risks and over-exposure in the market. It prevents simultaneous trade executions on quotes provided by the MM within a short time span. The MM can automatically pull their quotes if the number of contracts traded for an underlying asset exceeds the configured threshold within a certain time frame. Once MMP is triggered, any pre-existing MMP orders will be automatically canceled, and new orders tagged as MMP will be rejected for a specific duration — known as the frozen period — so that MM can reassess the market and modify the quotes.

How to enable MMP

Send an email to Bybit (financial.inst@bybit.com) or contact your business development (BD) manager to apply for MMP. After processed, the default settings are as below table:

ParameterTypeCommentsDefault value
baseCoinstringBase coinBTC
windowstringTime window (millisecond)5000
frozenPeriodstringFrozen period (millisecond)100
qtyLimitstringQuantity limit100
deltaLimitstringDelta limit100

Applicable

Effective for options only. When you place an option order, set mmp=true, which means you mark this order as a mmp order.

HTTP Request

POST /unified/v3/private/account/mmp-modify

Request Parameters

ParameterRequiredTypeComments
baseCointruestringBase coin
windowtruestringTime window (ms)
frozenPeriodtruestringFrozen period (ms). "0" means the trade will remain frozen until manually reset
qtyLimittruestringTrade qty limit (positive and up to 2 decimal places)
deltaLimittruestringDelta limit (positive and up to 2 decimal places)

Response Parameters

None

Request Example

POST /unified/v3/private/account/mmp-modify HTTP/1.1
Host: api.bybit.com
X-BAPI-SIGN: XXXXX
X-BAPI-API-KEY: XXXXX
X-BAPI-TIMESTAMP: 1675833524616
X-BAPI-RECV-WINDOW: 50000
Content-Type: application/json

{
"baseCoin": "ETH",
"window":"5000",
"frozenPeriod":"100000",
"qtyLimit":"50",
"deltaLimit":"20"
}

Response Example

{
"retCode": 0,
"retMsg": "success"
}