Bybit sub-account fee tier for API orders: which account rate applies?

What the subaccount inherits

The Standard Subaccount FAQ explicitly says trading-fee discounts applied to the Main Account are inherited by standard subaccounts. The trading-fee guide separately states that subaccounts automatically adopt the Main Account's fee structure. These two statements describe the same connection from the account-management and fee-policy sides.

That shared schedule does not combine every account record. The FAQ says a standard subaccount's profit and loss remains separate from the Main Account. Keep each strategy's execution and expense records with that strategy, even when several strategies receive the same fee tier. An aggregate account-level benefit and separate trading results can exist together.

Creating and maintaining a standard subaccount carries no fee under the FAQ. Transfers between the Main Account and standard subaccounts also carry no fee. Those account-management costs belong in separate lines from trading charges. A free internal transfer does not establish that the trade placed after it has a zero fee. Source: Bybit, “FAQ — Standard Subaccount,” bybit.com.

The same FAQ says deposits and withdrawals must go through the Main Account. The Main Account can transfer to and from its standard subaccounts and between two subaccounts. A standard subaccount can transfer in one direction to the Main Account. If you are budgeting a strategy's funding, distinguish its internal allocation from an external withdrawal.

For ordinary users the FAQ allows up to five standard subaccounts per Main Account; institutional users can create up to twenty. It says these counts exclude custodial subaccounts. The article concerns standard subaccounts. A managed arrangement described under a different account type needs its own terms checked before using these instructions.

Match the fee to the product before doing the arithmetic

Bybit's fee guide has separate sections for crypto-to-crypto spot, perpetual and futures contracts, options, and special trading zones. Its general spot table is expressly limited to crypto trading pairs. A fee copied from that row cannot answer a question about a fiat pair or a special zone without checking the matching table.

For a simple, sourced example, the base VIP 0 crypto-to-crypto spot table lists 0.1000% in both fee columns. The VIP 0 Adventure Zone table lists 0.2000% in both columns. These are published base rows, not an account quote. The same guide directs users to My Fee Rate after identity verification for the accurate rate, because actual rates can vary by region. Source: Bybit, “Trading Fee Structure,” bybit.com.

On a hypothetical $1,000 of completed trading value, 0.1000% produces a $1 fee and 0.2000% produces $2. The arithmetic is $1,000 × 0.001 and $1,000 × 0.002. The $1 difference comes entirely from changing the rate in this example. It says nothing about a price movement, an account's eligibility for a special trading zone, or the availability of a particular instrument.

SponsoredBybit

Partner rebate share30%Up to

Check regional eligibility and account terms

✓Code applied automatically by the sign-up link: 48553

Sign up on Bybit →Code48553Copied

If the same hypothetical strategy completes $10,000 of trading value, the calculation becomes $10 or $20. This is a budget comparison using the two published percentages. Use the amount actually filled and the fee currency shown in the account when checking a real trade. Keep an unfilled plan out of the completed-trade total.

For a purchase followed by a sale, budget each completed leg separately. Two hypothetical $1,000 legs at an assumed 0.1000% each sum to $2: $1 on the first leg and $1 on the second. If their values or applicable rates differ, calculate them separately before adding them. A single-trade estimate should not be labelled the cost of an entire round trip.

What this means for you: before the next API order

Bybit's official API documentation provides a Get Fee Rate account readout. Its request fields distinguish the product category and, where applicable, the symbol. The documented categories include spot, linear, inverse and option. This supports checking the rate relevant to a trading setup instead of hard-coding one percentage for every order.

The documentation's response example uses BTCUSDT and shows a rate of 0.001 in each of its two main fee fields. That is an example response, equivalent to 0.1% when expressed as a percentage. It is not a live quotation for your subaccount. Source: Bybit V5 documentation, Get Fee Rate.

• Record the account being queried, the product category, the symbol where used, the returned rate, and the observation time. Keep the percentage and decimal forms distinguishable in the worksheet. A displayed 0.1% enters multiplication as 0.001; using 0.1 would make the computed expense one hundred times too large.

• Read the account's rate through your existing authorized API setup and compare it with the rate assumed by the strategy. This comparison uses the current connection; it does not require changing permissions, creating another key, or submitting a test trade to check the inheritance rule.

If the strategy's budget uses a different rate, preserve both values and their timestamps before investigating. A current readout and an earlier order may refer to different moments. Bybit's fee guide makes order placement time relevant to the VIP level used for that order.

The 15:00 SGT refresh and trading-volume attribution

Bybit says VIP levels refresh daily at 07:00 UTC, which is 15:00 SGT. A strategy scheduled around that time should keep the order's placement time with the fee-tier record. The source specifies the refresh schedule and the order-time rule; it does not establish that every interface or a trader's own saved configuration refreshes simultaneously.

The fee guide says the VIP level is determined by asset balance or trading volume over the previous thirty days, with the qualifying higher tier used. It also says trading volume from the Main Account and Subaccount is considered. A subaccount's isolated trading result therefore should not be used as the complete record of account-wide VIP qualification.

There is a separate qualification detail for heavy API use. The published VIP criteria table attaches “API Trading Volume ≤ 20%” to the spot, derivatives and options trading-volume routes for VIP 4, VIP 5 and Supreme VIP. Read that condition alongside the relevant threshold. A large volume total by itself leaves out a stated part of those routes. Source: Bybit, “Trading Fee Structure,” VIP Criteria table, bybit.com.

The condition should remain tied to those specific table entries. It does not establish a twenty-percent fee, a surcharge of twenty percent, or a universal cap on API trading. Asset-balance routes appear separately in the table. If you are comparing ways an account might qualify, preserve the route as well as the tier name.

Bybit also excludes zero-fee spot trades from total spot trading volume for this purpose. Funding fees received or paid do not count toward trading volume. These exclusions matter when a strategy's own turnover worksheet disagrees with the quantity being used for qualification. Reconcile the categories before assuming that the account has missed a tier refresh.

A worksheet for two strategies sharing one Main Account

Consider a hypothetical Main Account with two standard subaccounts, one for ordinary crypto spot and one for a different trading zone. Begin each strategy's worksheet with its own account label and product. Copying a common VIP tier into both sheets is consistent with the inheritance rule. Copying one product's percentage into the other sheet skips the product check.

Now assume the first strategy records $6,000 of completed value at 0.1000%. Its example charge is $6. Assume the second records $4,000 at 0.2000%; its example charge is $8. The combined budget is $14 on $10,000 of value, or 0.14% by arithmetic. These assumed rates reproduce the base spot examples above; they do not identify a reader's current tier.

That 0.14% describes the combined hypothetical expense. It should not replace either strategy's own rate in the next order calculation. With the same $10,000 total split differently across the two assumed rates, the combined expense would change. Keep the product-level rows so the total can be explained.

For a real review, put the charged amount and charged asset beside each completed trade. If you later convert costs into one reporting currency, retain the conversion inputs separately. This avoids attributing an exchange-rate movement in your report to a change in Bybit's fee tier. Our Bybit fee and account profile provides the venue overview for comparing these records with other account arrangements.

Quick answers before the next API order

Does a newly created standard subaccount start from its own fee tier?

Bybit's two official guides say it adopts the Main Account's fee structure and inherits its trading-fee discounts. Check the rate shown for the intended product rather than assigning a fresh tier because the subaccount is new.

Is creating the subaccount itself a trading expense?

The Standard Subaccount FAQ says creation and maintenance are free, and internal transfers between the Main Account and standard subaccounts carry no fee. Record actual trading charges separately.

Does a large API turnover automatically establish VIP 4 or higher?

The published table puts an API-volume-share condition on particular trading-volume qualification routes at VIP 4, VIP 5 and Supreme VIP. Compare the complete route, including that condition, with the account's qualification record.

Which number belongs in the next order's budget?

Use the account-specific rate for the correct product, preserve the observation time, and calculate the expected expense from the intended filled value. After execution, compare that estimate with the actual charged amount and currency in the trade record.