Order Flow Snapshot
Under maintenancePricing
$0.05 / order flow snapshot
Order Flow Snapshot
Under maintenanceRetrieve exchange order-flow observations with price, bid and ask arrays. Export timestamped JSON for trading-pair research.
Pricing
$0.05 / order flow snapshot
Rating
0.0
(0)
Developer
Grass Tech
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
12 days ago
Last modified
Categories
Share
Retrieve exchange order-flow observations with price, bid and ask arrays. Export timestamped JSON for trading-pair research.
What this Actor does
Inspect price-level order-flow observations for a trading pair and historical interval. Each run is a bounded request, not a live trading signal.
Input
| Field | Type | Required | Description |
|---|---|---|---|
exchange | string | Yes | Exchange selector. Verified example: Binance. |
symbol | string | Yes | Trading-pair symbol. Verified example: BTCUSDT. |
interval | string | Yes | Observation interval as a string. Use the verified spelling in the example input. |
endTime | string | Yes | End timestamp in Unix milliseconds, supplied as a string. The example is historical, not the current time. |
size | string | Yes | Requested observation count as a string. Verified example: 10; availability may reduce the returned count. |
productType | string | Yes | Market-type selector. Verified value: SWAP. |
tickCount | string | Yes | Price-level query parameter as a string. Verified value: 1. |
Example input
{"endTime": "1789544653328","exchange": "Binance","interval": "1h","productType": "SWAP","size": "10","symbol": "BTCUSDT","tickCount": "1"}
This input was used for the saved successful run on September 16, 2026. Historical timestamps are examples; update them for your desired period. Supported markets and data coverage depend on the selected parameters. Unsupported combinations can return empty data or errors.
Output
The response contains code, success and data. Observed rows include exchangeName, symbol, ts, prices, bids and asks. The three arrays share the same length in the saved response; pair their values by index. Counts and quantity units are not independently labelled in the payload.
Example output
Abbreviated from the September 16, 2026 response. This is historical data, not a current quote. Rows, series and fields have been omitted for readability.
{"code": "1","data": [{"asks": [0,1,8.6],"bids": [8.9,4.3,0.1],"exchangeName": "Binance","prices": [75710.1,75710,75709.9],"symbol": "BTCUSDT","ts": 1789509600000}],"success": true}
A successful run saves its JSON result under OUTPUT. Open the Output tab to inspect response status, fields and available timestamps.
Pricing
One request event is $0.05. Review the current Pricing panel and set a maximum run charge that covers the event. Check any platform usage displayed before starting.
How to run
- Review the required fields and update the example input.
- Check the current price and run budget.
- Start one run and wait for its final status.
- Open Output and inspect the response before using it in a report or workflow.
Scope and troubleshooting
Each run performs one data query. Data availability and freshness vary by market and query parameters. This Actor does not execute trades, move funds or maintain a live subscription.
If a run fails, inspect its status and log before retrying. For support, open an Actor Issue with the Run ID and sanitized input; omit credentials and private keys. Financial data is informational, not investment advice.