Bybit Scraper avatar

Bybit Scraper

Pricing

from $1.00 / 1,000 records

Go to Apify Store
Bybit Scraper

Bybit Scraper

Extract live Bybit spot prices for any pair with no API key: last, best bid and ask with their sizes, 24h high, low, base volume and quote turnover, and the 24h change on the exchange clock. Export data, run via API, schedule and monitor runs, or integrate with other tools.

Pricing

from $1.00 / 1,000 records

Rating

5.0

(1)

Developer

Public Money

Public Money

Maintained by Apify

Actor stats

1

Bookmarked

4

Total users

3

Monthly active users

21 hours ago

Last modified

Categories

Share

Bybit's REST API needs a key and a signed request for anything beyond the public feed, and it is unavailable in several countries. This Actor reads the public spot ticker for any pair and returns one structured record: last price, best bid and ask with their sizes, 24h high, low, volume, turnover and change. No key, no signature, no SDK.

What it does

  • Returns one record per requested pair, in order. A pair Bybit does not list comes back with status: "failed" and a reason, so a batch never fails silently.
  • Carries bid and ask sizes, not just the prices, so you can see how thin the top of the book is before you act on a spread.
  • Keeps both names: requested is what you asked for (BTC/USDT) and symbol is Bybit's own (BTCUSDT).
  • Reports 24h turnover in the quote asset next to volume in the base asset, which is the comparison most dashboards actually want.
  • Routes through Germany because Bybit restricts a number of jurisdictions. The egress the source needs is handled for you and there is nothing to configure.
  • Needs no API key and no signed request.

Use cases

You need toHow this Actor does it
Price a portfolio every minutePass every pair you hold and schedule the run
Watch the spread on a pairSubtract bid from ask on each run and alert on a widening book
Check depth before tradingRead bidSize and askSize next to the spread
Compare venues for the same pairRun this next to the Binance, OKX, Kraken or Coinbase Actor and diff value at validFrom
Feed a trading agentCall the Actor over MCP and let the model ask for the pair it needs
Build your own candlesSchedule the run and let the dataset accumulate one row per pair per run

Quick start

  1. Click Try for free.
  2. Add your pairs, one per line, as BASE/QUOTE: BTC/USDT, ETH/USDT, SOL/USDT. Bybit quotes most spot pairs in USDT.
  3. Click Start. Rows appear within seconds.
  4. Export as JSON, CSV, Excel or XML, or read the dataset over the API.

Input

FieldTypeDefaultWhat it controls
pairsarrayBTC/USDT, ETH/USDTTrading pairs to read, written BASE/QUOTE. Slashes are optional and case does not matter.
maxItemsinteger0Caps how many pairs are read. 0 reads them all
{
"pairs": [
"BTC/USDT",
"ETH/USDT",
"SOL/USDT"
],
"maxItems": 0
}

Output

One dataset item per pair. Fields Bybit does not publish for a pair are dropped rather than returned as null.

Field groupFields
Identitystatus, requested, symbol, currency, url
Pricevalue, bid, ask
24 hour windowhigh24h, low24h, baseVolume24h
TimingvalidFrom, scrapedAt
Book depthbidSize, askSize, quoteVolume24h, changePercent24h
{
"status": "ok",
"requested": "BTC/USDT",
"symbol": "BTCUSDT",
"currency": "USDT",
"value": 104231.4,
"bid": 104231.3,
"ask": 104231.4,
"bidSize": 2.415,
"askSize": 1.882,
"high24h": 106540.0,
"low24h": 103112.45,
"baseVolume24h": 9214.77,
"quoteVolume24h": 963442188.1,
"changePercent24h": -1.84,
"validFrom": "2026-09-04T20:00:01.000Z"
}

Integrations

Run it over the API and get the rows back in one call:

curl -X POST "https://api.apify.com/v2/acts/publicmoney~bybit-scraper/run-sync-get-dataset-items?token=YOUR_TOKEN" \
-H "Content-Type: application/json" \
-d '{"pairs": ["BTC/USDT", "ETH/USDT", "SOL/USDT"], "maxItems": 0}'

From Python:

from apify_client import ApifyClient
client = ApifyClient("YOUR_TOKEN")
run = client.actor("publicmoney/bybit-scraper").call(run_input={"pairs": ["BTC/USDT", "ETH/USDT", "SOL/USDT"], "maxItems": 0})
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
print(item["symbol"], item["value"], item["validFrom"])

Give an AI agent the Actor over MCP:

{
"mcpServers": {
"apify": {
"url": "https://mcp.apify.com/?actors=publicmoney/bybit-scraper"
}
}
}

Schedules run it on any cron, webhooks fire when a run finishes, and platform integrations push the dataset to Google Sheets, Slack, Airtable, Zapier or your own endpoint.

Cost

Pay per event, so you pay for records rather than compute time.

EventFree tierTop volume tier
Record with data$0.002$0.0007
Actor start$0.00005 per GBSame

A record that returned no data is published as a failure row and is never charged. Six volume tiers apply, so the per-record price falls with monthly volume.

Troubleshooting

IssueSolution
Every pair returns failedBybit is refusing the egress this Actor uses. It is not settable from the input, so open an issue on the Issues tab and we will move it.
One pair returns failed, the rest are fineThat pair is not listed on this exchange, or the quote asset is wrong. Check it on the exchange first.
symbol does not match what I sentBy design. requested is your input and symbol is Bybit's own form, so BTC/USDT becomes BTCUSDT.
Volume looks wrong next to another exchangeCheck which one you are reading. baseVolume24h is in the base asset and quoteVolume24h is turnover in the quote asset.
value looks behind another exchangeRead validFrom. It is the exchange's own timestamp for that tick, so two venues legitimately differ. Prices are spot, not aggregated.

FAQ

Does the Bybit API need an API key?

For account and trading endpoints yes, with a signed request. The public spot ticker does not, which is what this Actor reads.

Why is Bybit unavailable in my country?

Bybit restricts access from a number of jurisdictions and returns an error rather than data. This Actor routes through Germany for that reason, and the egress is not exposed in the input.

Is this the real-time Bybit price?

It is the last trade Bybit published at validFrom, read live on each run. It is not a stream, so for tick-by-tick data use a websocket. For a price every minute or every hour, schedule the Actor.

Does it return Bybit candles or historical prices?

No. Each record is the current ticker. To build a series, schedule the Actor and let the dataset accumulate one row per pair per run, each stamped with validFrom.

Can it read Bybit derivatives?

No. This Actor covers the spot market. For perpetual funding rates use the Binance Actor in this fleet, which carries them for the pairs Binance lists.

Do I need a Bybit API key?

No. You need an Apify token to call the Actor over the API. No Bybit credential is involved anywhere.

Can I get this data in Python?

Yes, with the apify-client package as shown above. It returns parsed JSON, so there is no HTML or response handling on your side.

Can I get the data into Excel or Google Sheets?

Yes. Export the dataset as XLSX or CSV, or connect the Google Sheets integration so each run appends to a sheet.

Can an AI agent call this Actor?

Yes. Add it to an MCP client with the config above and the model can request what it needs on its own. Every record is flat JSON with named fields, so no post-processing is needed.

This Actor reads public Bybit data that needs no login and collects no personal data. Scraping public data is generally lawful, and how you store, redistribute or act on market data is governed by your own agreements and local rules. Take your own legal advice for your use case.

Changelog

  • 0.0.2 Added bid and ask sizes and 24h turnover in the quote asset.
  • 0.0.1 First release. Spot ticker for any listed pair.

Feedback

Found a field Bybit publishes that this Actor misses, or an input it rejects? Open an issue on the Issues tab with the input and what you expected. A daily test runs every Actor in the fleet against live sources, so parser fixes ship fast.