Vimeo Tutorial How to Use

Gate to Historic One Minute Bitcoin Pricing 

Historic Bitcoin Price by Minute

To use the quick and easy API click on the image to see a Vimeo tutorial.  It is easy, just head over to rapidAPI and get yourself a logon and API key.  The code snippets are provided so you can just copy the snippet into your script .

Historic Bitcoin Price by Time API Specification

Rest API endpoints.  Simplicity:  These are Rest 'GET' endpoints with no user verification needed at this point.    The api's are hosted on rapidAPI.  

1.)  Go to rapidAPI and get a user ID and API key.
2.)  Go to the hub https://rapidapi.com/macmiller/api/historic-bitcoin-price
3.)  When you click on test endpoint you can see the results for a particular test case.
4.)  Copy the Code Snippet you need for your application.  

GET BTC PRICE POINT

The point of the 'get BTC price point' endpoint is to return the BTC price for a particular point in time as specified in the request. This will be the main endpoint of interest to the end user. The idea is to be able to retrieve the BTC price, collected from multiple sources, for a particular point in time.

Endpoint:
http://historic-bitcoin-price.p.rapidapi.com/api_btc_pull/api.php?action=price_retrieval ...

date = requested date, YYYY-MM-DD format
time = requested time, HH:MM 24 hr clock
timezone = timezone, see valid timezones
setting_flag = flag, B = before, A = after, C = closest

Example Request:
http://historic-bitcoin-price.p.rapidapi.com/api_btc_pull/api.php?action=price_retrieval&date=2021-04-19&time=17:04&setting_flag=C&timezone=Asia/Bangkok

Example Return JSON package:
{"response_code":"200","response_desc":"requested data supplied","data":{"interval":"00:00:00:00:00:01:000000","date_used":"2021-04-19 17:04:01","date_requested":"2021-04-19 17:04:00","timezone_used":"Asia_Bangkok","BTCUSD_from_COI":"56667.5602","BTCUSD_from_GEM":"56626.62","BTCUSD_from_KRA":"56642.2","BTCUSD_from_BIN":"56615","BTCUSD_from_avg":"56637.84505"}}

Meaning:
The endpoint requested the Bitcoin price as of April 19th, 2021 at 5:04PM in the timezone Asia/Bangkok. (Refer to list of supported timezones for allowed values). The flag setting (fl = C) indicates the closest collected value to the 5:04PM time should be returned (either before or after 5:04PM on April 19th, 2021).

The returned data indicates that a data value was located 1 second ("interval":"00:00:00:00:00:01:000000") away from the requested value. Note; interval format is %Y:%M:%D:%H:%I:%S:%F -- the right most group in microseconds, the next group the the left is seconds and the group to the left of this is minutes. The other values should normally be zero. The requested time was April 19th, 2021 at 5:04PM. A data snapshot had been preserved in the database on April 19th, 2021 at 5:04:01PM. All times indicated are in the timezone specified in the API request (in this case tz=ASIA/Bangkok). The prices returned are as follows:
BTCUSD_from_COI
BTCUSD_from_GEM
BTCUSD_from_KRA
BTCUSD_from_BIN
with an average indicated by BTCUSD_from_avg.

VERIFY

The point of the 'verify' endpoint is to examine the existing data to ensure that data points have been continually collected without any gaps, in other words:
Data collection is really happening and reliable.  This is an audit and verification task that mostly will be performed to ensure that the data collection is adequate for the desired functionality.  It answers questions like how often is the data collected and what is the earliest date that data collection begins.   

Endpoint:
http://historic-bitcoin-price.p.rapidapi.com/api_btc_pull/api.php?action=verify ..

verify=yes : indicates that the endpoint is to verify the database is loaded since a particular point in time
number_of_minutes: defaults to 11. The number of minutes allowed between data collection points to ascertain the starting and first date in the series.
time_delay_in_hours: defaults to 24. The data is normally collected in four separate nodes at 10 minute intervals, with each node having a different minute offset. One node my snapshot data at a two minute offset, so 5:02, 5:12, 5:22, 5:32 etc.  Another node may snapshot data at a four minute offset so 5:04, 5:14, 5:24, 5:34 etc.  The data is the pulled over to a central node once a day (at this time). This means that on the current day the data may not have been pulled over yet. This parameter indicates that when scanning the collected data, the scan will be through the current point in time minus the indicated number of hours, for the purpose of ascertaining the starting date.
verify_timezone: defaults to Asia/Bangkok. The full list of supported timezones can be seen here: list of supported timezones . The actual data in the database is in 'GMT' format. By indicating another timezone the returned data and time will be displayed in that time zone.

Example Request:
http://historic-bitcoin-price.p.rapidapi.com/api_btc_pull/api.php?action=verify&number_of_minutes=72&time_delay_in_hours=24&verify_timezone=Asia/Aden

Example Return JSON package:
{"response_code":"200","response_desc":"requested data supplied","data":{"number of records":2696,"earliest date with integrity":"2021-04-23 09:52:01","interval min. for checking":"12","time delay in hours":"24","timezone used":"Asia_Aden"}}

Meaning:
The main data collection point has been scanned from the beginning of time until the current point in time minus 24 hours (time_delay_in_hours). There is continuous data in the table indicating the bitcoin price with no gap more than 12 minutes (number_of_minutes). The first data point is on April 23rd, 2021 at 09:41:01 AM displayed in Asia/Aden timezone (verify_timezone).


  

© Copyright 2025 Historic Bitcoin Price - All Rights Reserved