Introduction to Crypto Sentiment API and other API endpoints
Welcome to BittsAnalytics API documentation.
BittsAnalytics is a high-quality platform which provides real-time, reliable and unique data REST APIs for the cryptocurrency market.
We are one of the oldest analytics platforms in the crypto world, delivering crypto data since 2017.
We specialise in providing data sets with high impact on prices of digital assets: social media sentiment, social media mentions, news sentiment and other categories of data, with our APIs being used by hedge funds, mobile apps, crypto funds, news platforms and individual clients.
We provide the following types of data for the cryptocurrency market:
- Social Media Sentiment
- Social Media Mentions
- News (sentiment classified)
- Crypto Fear & Greed Index
- Investor Sentiment and Social Buzz Indices (tracking opinions of investors, traders, hedge funds and other professional investors)
- Price support and resistance levels
- Trendlines (with alerts for cryptocurrencies that are currently breaking their trendlines)
- Historical Bull and Bear Markets for each cryptocurrency
- Social momentum scores
- Influencer Sentiment And Mentions Indices (with influencers segmented based on their number of followers)
Authentication
BittsAnalytics uses API keys to allow access to the API. You can obtain a new BittsAnalytics API key by purchasing subscription to Advanced or Professional Plan.
BittsAnalytics expects for the API key to be included in all API requests to the server in a header that looks like the following:
X-api-key: b4dade2ce5fb2d0b189b5eb6f0cd
HTTP responses that are successful will have the status code 200 and the response formatted according to specification, please consult our documentation for further details.
API requests are limited at 10 requests per unit interval of 10 seconds. API requests limits are set according to combination of your IP and API key. If you will exceed the API limits you will be notified with message 'Too many requests'.
Our servers return API data in JSON format by default.
Real-time data for coins
Real-time data endpoint includes the following categories:
timestamp: datetime,
ticker: symbol of cryptocurrency,
price_usd: price of cryptocurrency in USD,
market_cap: market capitalization of cryptocurrency in USD,
trading_volume: trading volume of cryptocurrency in USD (last 24 hours),
momentum score: proprietary indicator calculated as equal-weighted z-scores (from population of 200+ cryptocurrencies) for the following categories: 24 hour change in price, change in daily sentiment, change in daily number of mentions, change in daily trading volume. Momentum score indicates the composite momentum of a cryptocurrency in price, trading volume, social media sentiment and social media buzz.
hourly_social_sentiment: we calculate social media sentiment of coins by using advanced machine learning models from texts of social media posts on twitter that mention individual coins. Hourly social sentiment is the average sentiment of a coin in the last closed hour in UTC time.
hourly_social_mentions: we calculate number of mentions of coins in texts of social media posts on twitter. Hourly social mentions is the number of mentions of a given coin in the last closed hour in UTC time.
hourly_social_buzz: is the number of mentions of coins on twitter in last 3 hours normalized by historical, similar 3 hour windows. Hourly social buzz indicates how much is the coin mentioned on social media recently as compared to historical averages for this coin.
hourly_social_sentiment_momentum: is the average sentiment of coins on twitter in last 3 hours normalized by historical, similar 3 hour windows. Hourly social sentiment momentum indicates how positive or negative is the sentiment of coin as compared to historical averages for this coin.
daily_social_sentiment: is the average sentiment of coin on twitter in last closed day in UTC time.
daily_social_mentions: is the number of mentions of a given coin in last closed day in UTC time.
HTTP Request
GET https://www.bittsanalytics.com/bittsanalytics/api3.php/rankings_api \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl https://www.bittsanalytics.com/bittsanalytics/api3.php/rankings_api \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"rankings_api": {
"columns": [
"timestamp",
"ticker",
"price_usd",
"market_cap",
"trading_volume",
"momentum_score",
"hourly_social_sentiment",
"hourly_social_mentions",
"hourly_social_buzz",
"hourly_social_sentiment_momentum",
"daily_social_sentiment",
"daily_social_mentions",
"volatility"
],
"records": [
[
"2021-11-03 18:00:01",
"1INCH",
4.41,
796271535,
128554169,
-0.1,
0.4284,
62,
-0.74869633960069,
-0.18135044903316,
0.36744,
2483,
6.5896631195991
],
[
"2021-11-03 18:00:01",
"AAVE",
318.23,
4212745920,
284133431,
-0.11,
0.30595,
23,
-0.89477182710337,
-0.24977844159565,
0.31559,
864,
3.5947769673612
],
[
"2021-11-03 18:00:01",
"ADA",
2.05,
65957358656,
3807094058,
-0.02,
0.30777,
646,
-0.66014996720593,
-0.3123413360723,
0.22999,
19228,
3.1545147247885
],
[
"2021-06-03 00:00:00",
"AE",
0.17523926168773,
1,
1,
-0.22,
0,
0,
1.7185024366432,
0.21864250708751,
-0.1816,
2,
5.640027467279
],
[
"2021-11-03 17:00:01",
"ALGO",
1.9,
11830191895,
390412892,
-0.17,
0.17769,
209,
-1.2394591883684,
-0.027101381244916,
0.17479,
4157,
4.7143420885473
],
[
"2021-11-03 18:00:01",
"ALPHA",
1.14,
507882740,
38506801,
0.37,
0.772,
3,
-0.59513635259157,
-0.12129826981293,
0.26554,
274,
4.7893064272875
],
[
"2021-11-03 18:00:01",
"AMPL",
1.84,
433034168,
10237489,
0.12,
0.04526,
22,
-0.63589199085325,
-0.256405131229,
0.29746,
319,
8.9822759446876
],
[
"2021-11-03 18:00:01",
"ANKR",
0.126118,
1030125133,
234903969,
-0.14,
0.39518,
27,
-0.53852706036192,
-1.739064635448,
0.32458,
3013,
6.3502791061554
],[.......]
]
}
}
Daily Social Sentiment
Daily Social Sentiment API Endpoint provides access to historical daily sentiment data. Our historical data for daily latency starts on 14 August 2017. Daily social sentiment is the average sentiment of social media posts mentioning cryptocurrency in last closed day in UTC time. Sentiment is determined by appyling advanced machine learning models on texts of social media posts that mention individual coins.
HTTP Request
GET https://www.bittsanalytics.com/bittsanalytics/api3.php/sentiment \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Example of daily social sentiment (from our dashboard):
curl "https://www.bittsanalytics.com/bittsanalytics/api3.php/sentiment?filter[]=datum,bt,2021-08-01,2021-08-28&filter[]=valuta,eq,BTC" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"sentiment": {
"columns": [
"valuta",
"datum",
"index"
],
"records": [
[
"BTC",
"2021-08-01",
"0.28147"
],
[
"BTC",
"2021-08-02",
"0.18143"
],
[
"BTC",
"2021-08-03",
"0.18965"
],
[
"BTC",
"2021-08-04",
"0.25334"
],
[
"BTC",
"2021-08-05",
"0.27087"
],
[
"BTC",
"2021-08-06",
"0.29711"
],
[
"BTC",
"2021-08-07",
"0.33982"
],
[
"BTC",
"2021-08-08",
"0.31848"
],
[
"BTC",
"2021-08-09",
"0.23502"
],
[
"BTC",
"2021-08-10",
"0.28567"
],
[
"BTC",
"2021-08-11",
"0.30631"
],
[
"BTC",
"2021-08-12",
"0.23686"
],
[
"BTC",
"2021-08-13",
"0.26641"
],
[
"BTC",
"2021-08-14",
"0.39119"
],
[
"BTC",
"2021-08-15",
"0.21183"
],
[
"BTC",
"2021-08-16",
"0.23152"
],
[
"BTC",
"2021-08-17",
"0.18140"
],
[
"BTC",
"2021-08-18",
"0.18399"
],
[
"BTC",
"2021-08-19",
"0.18045"
],
[
"BTC",
"2021-08-20",
"0.26914"
],
[
"BTC",
"2021-08-21",
"0.33920"
],
[
"BTC",
"2021-08-22",
"0.32542"
],
[
"BTC",
"2021-08-23",
"0.40742"
],
[
"BTC",
"2021-08-24",
"0.33542"
],
[
"BTC",
"2021-08-25",
"0.31915"
],
[
"BTC",
"2021-08-26",
"0.22654"
],
[
"BTC",
"2021-08-27",
"0.21264"
],
[
"BTC",
"2021-08-28",
"0.24095"
]
]
}
}
Daily Number of Social Mentions
Daily Social Mentions API Endpoint provides access to historical daily mentions of individual cryptocurrencies on social media. Our historical data starts on 14 August 2017.
HTTP Request
GET https://www.bittsanalytics.com/bittsanalytics/api3.php/volume \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Example of daily social mentions (from our dashboard):
curl "https://www.bittsanalytics.com/bittsanalytics/api3.php/volume?filter[]=datum,bt,2021-08-01,2021-08-28&filter[]=valuta,eq,BTC" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"volume": {
"columns": [
"valuta",
"datum",
"volume"
],
"records": [
[
"BTC",
"2021-08-01",
100149
],
[
"BTC",
"2021-08-02",
109165
],
[
"BTC",
"2021-08-03",
92769
],
[
"BTC",
"2021-08-04",
96819
],
[
"BTC",
"2021-08-05",
104496
],
[
"BTC",
"2021-08-06",
107098
],
[
"BTC",
"2021-08-07",
108501
],
[
"BTC",
"2021-08-08",
94356
],
[
"BTC",
"2021-08-09",
123140
],
[
"BTC",
"2021-08-10",
122645
],
[
"BTC",
"2021-08-11",
117687
],
[
"BTC",
"2021-08-12",
100220
],
[
"BTC",
"2021-08-13",
107926
],
[
"BTC",
"2021-08-14",
105666
],
[
"BTC",
"2021-08-15",
95518
],
[
"BTC",
"2021-08-16",
107666
],
[
"BTC",
"2021-08-17",
107999
],
[
"BTC",
"2021-08-18",
121507
],
[
"BTC",
"2021-08-19",
100939
],
[
"BTC",
"2021-08-20",
110225
],
[
"BTC",
"2021-08-21",
110679
],
[
"BTC",
"2021-08-22",
113381
],
[
"BTC",
"2021-08-23",
167612
],
[
"BTC",
"2021-08-24",
158458
],
[
"BTC",
"2021-08-25",
200000
],
[
"BTC",
"2021-08-26",
121499
],
[
"BTC",
"2021-08-27",
121846
],
[
"BTC",
"2021-08-28",
90771
]
]
}
}
Hourly Social Sentiment
Hourly Social Sentiment API Endpoint provides access to historical hourly social media sentiment data for individual coins.
HTTP Request
GET https://www.bittsanalytics.com/bittsanalytics/api3.php/sentiment_h \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Example of hourly social sentiment (from our dashboard):
curl "https://www.bittsanalytics.com/bittsanalytics/api3.php/sentiment_h?filter[]=datum,bt,2021-08-01,2021-08-02&filter[]=valuta,eq,BTC" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{{
"sentiment_h": {
"columns": [
"valuta",
"datum",
"index"
],
"records": [
[
"BTC",
"2021-08-01 00:00:00",
"0.35535"
],
[
"BTC",
"2021-08-01 01:00:00",
"0.32643"
],
[
"BTC",
"2021-08-01 02:00:00",
"0.35605"
],
[
"BTC",
"2021-08-01 03:00:00",
"0.32406"
],
[
"BTC",
"2021-08-01 04:00:00",
"0.19697"
],
[
"BTC",
"2021-08-01 05:00:00",
"0.04119"
],
[
"BTC",
"2021-08-01 06:00:00",
"0.29018"
],
[
"BTC",
"2021-08-01 07:00:00",
"0.27849"
],
[
"BTC",
"2021-08-01 08:00:00",
"0.27974"
],
[
"BTC",
"2021-08-01 09:00:00",
"0.31748"
],
[
"BTC",
"2021-08-01 10:00:00",
"0.36726"
],
[
"BTC",
"2021-08-01 11:00:00",
"0.37987"
],
[
"BTC",
"2021-08-01 12:00:00",
"0.33859"
],
[
"BTC",
"2021-08-01 13:00:00",
"0.35913"
],
[
"BTC",
"2021-08-01 14:00:00",
"0.28755"
],
[
"BTC",
"2021-08-01 15:00:00",
"0.27687"
],
[
"BTC",
"2021-08-01 16:00:00",
"0.35180"
],
[
"BTC",
"2021-08-01 17:00:00",
"0.28349"
],
[
"BTC",
"2021-08-01 18:00:00",
"0.34966"
],
[
"BTC",
"2021-08-01 19:00:00",
"0.25741"
],
[
"BTC",
"2021-08-01 20:00:00",
"0.16929"
],
[
"BTC",
"2021-08-01 21:00:00",
"0.16422"
],
[
"BTC",
"2021-08-01 22:00:00",
"0.17141"
],
[
"BTC",
"2021-08-01 23:00:00",
"0.23273"
],
[
"BTC",
"2021-08-02 00:00:00",
"0.12804"
]
]
}
}
Hourly Number of Social Mentions
Hourly Social Mentions API Endpoint provides access to historical hourly mentions of individual cryptocurrencies on social media.
HTTP Request
GET https://www.bittsanalytics.com/bittsanalytics/api3.php/volume_h \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Example of hourly social mentions (from our dashboard):
curl "https://www.bittsanalytics.com/bittsanalytics/api3.php/volume_h?filter[]=datum,bt,2021-08-01,2021-08-28&filter[]=valuta,eq,BTC" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"volume_h": {
"columns": [
"valuta",
"datum",
"volume"
],
"records": [
[
"BTC",
"2021-08-01 00:00:00",
3250
],
[
"BTC",
"2021-08-01 01:00:00",
3921
],
[
"BTC",
"2021-08-01 02:00:00",
3095
],
[
"BTC",
"2021-08-01 03:00:00",
2899
],
[
"BTC",
"2021-08-01 04:00:00",
3590
],
[
"BTC",
"2021-08-01 05:00:00",
5752
],
[
"BTC",
"2021-08-01 06:00:00",
3035
],
[
"BTC",
"2021-08-01 07:00:00",
2987
],
[
"BTC",
"2021-08-01 08:00:00",
3325
],
[
"BTC",
"2021-08-01 09:00:00",
2989
],
[
"BTC",
"2021-08-01 10:00:00",
3882
],
[
"BTC",
"2021-08-01 11:00:00",
3620
],
[
"BTC",
"2021-08-01 12:00:00",
2757
],
[
"BTC",
"2021-08-01 13:00:00",
3261
],
[
"BTC",
"2021-08-01 14:00:00",
4442
],
[
"BTC",
"2021-08-01 15:00:00",
4638
],
[
"BTC",
"2021-08-01 16:00:00",
5297
],
[
"BTC",
"2021-08-01 17:00:00",
5568
],
[
"BTC",
"2021-08-01 18:00:00",
6335
],
[
"BTC",
"2021-08-01 19:00:00",
5737
],
[
"BTC",
"2021-08-01 20:00:00",
6669
],
[
"BTC",
"2021-08-01 21:00:00",
3964
],
[
"BTC",
"2021-08-01 22:00:00",
5287
],
[
"BTC",
"2021-08-01 23:00:00",
3849
],
[
"BTC",
"2021-08-02 00:00:00",
3480
]
]
}
}
Crypto Fear and Greed Index
Crypto Fear & Greed Index tries to capture positive and negative emotions of traders, investors and other persons interested in cryptocurrency market. It is based on determination of sentiment polarity of social media posts that are published about Bitcoin, Altcoins, Defi coins and other cryptocurrencies. Each day we determine social media sentiment of millions of social media posts about the crypto ecosystem, using a sentiment classification machine learning model.
Our Crypto Fear and Greed Index is published daily (for the previous close day in UTC time) and can take a value on a scale from 0 to 100. Based on value of the index, we distinguish betweetn five distinct market cycles of crypto market: extreme greed, greed, neutral, fear and extreme fear.
History of our Crypto Fear & Greed Index starts in August 2017.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/crypto_fear_greed_index \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_fear_greed_index" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Example of historical chart for BittsAnalytics Crypto Fear & Greed Index:
Example of current value of BittsAnalytics Crypto Fear & Greed Index:
The above command returns JSON structured like this:
{
"crypto_fear_greed_index": {
"columns": [
"ticker",
"datum",
"vrednost",
"crypto_fear_greed_index_class",
"zscore"
],
"records": [
[
"total_market",
"2017-08-13",
73.496668170015,
"greed",
0.62790429594074
],
[
"total_market",
"2017-08-14",
77.562073296177,
"greed",
0.75748636095847
],
[
"total_market",
"2017-08-15",
40.603251295947,
"neutral",
-0.23776286022735
],
[
"total_market",
"2017-08-16",
38.308258297757,
"neutral",
-0.29739473089218
],
[
"total_market",
"2017-08-17",
13.699597224091,
"fear",
-1.0939157179298
],
[
"total_market",
"2017-08-18",
3.3855996151823,
"extreme fear",
-1.8269187123941
],.....
]
}
}
News with sentiment classification
News with sentiment classification API Endpoint provides access to sentiment classified news. Our news sentiment annotated history dataset starts in 2018 and consists of over 200k news items. Each news is tagged for the cryptocurrencies that are mentioned in the text of news item.
We determine sentiment of both the title of news as well sentiment of news item text.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api_news.php/ttrss_entries?filter[]=id,eq,228150 \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl "http://bittsanalytics.com/bittsanalytics/api_news.php/ttrss_entries?filter[]=id,eq,228152" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Example of sentiment classified news items (from our dashboard):
The above command returns JSON structured like this:
{
"ttrss_entries": {
"columns": [
"id",
"title",
"guid",
"link",
"updated",
"content",
"content_hash",
"cached_content",
"no_orig_date",
"date_entered",
"date_updated",
"num_comments",
"plugin_data",
"lang",
"comments",
"author",
"sentiment_title",
"sentiment_text"
],
"records": [
[
228152,
"EOS, Synthetix, Maker Price Analysis: 16 April",
"SHA1:7d1cb764feb89b1a7fa97fea427f22516f0b6d3e",
"https://ambcrypto.com/eos-synthetix-maker-price-analysis-16-april/",
"2021-04-16 19:00:37",
"EOS can be expected to find strong support around the $6.8-zone. If Bitcoin stabilizes above the $60.5k-area, altcoins could have a chance of recovery in the coming days. Otherwise, it would be further selling pressure across the market. Synthetix and Maker posted gains over the past few days, but were likely to retrace a significant […]",
"057b7b8c85d1349dc98cbbadc4501f745cce0a9e",
null,
0,
"2021-04-16 19:05:00",
"2021-04-17 14:35:07",
0,
"",
"en",
"https://ambcrypto.com/eos-synthetix-maker-price-analysis-16-april/#respond",
"Akashnath Sumukar",
1,
0.75
]
]
}
}
Support and Resistance Levels
We compute support and resistance levels by taking into account: 1) how long has the security price been in certain range, 2) how much trading volume has been realized in this range. The higher is the product of both factors for given price range - level, the stronger is its intensity.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/bands \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl "http://bittsanalytics.com/bittsanalytics/api3.php/bands" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Example of support and resistance levels (from our dashboard):
Support and resistance levels are computed from price bands (from our dashboard):
The above command returns JSON structured like this:
{
"bands": {
"columns": [
"ticker",
"bottom",
"top",
"color_code",
"intensity"
],
"records": [
[
"PAX",
1.009442132129,
1.0097666872185,
"#FFFFFF",
0
],
[
"PLBT",
7.9406565978518,
8.0089800951473,
"#FFFFFF",
0
],
[
"QKC",
0.051153813768088,
0.051588906884044,
"#FFF6F6",
0.037276800674308
],
[
"RLC",
15.956127427886,
16.101197670592,
"#FFFFFF",
0
],
[
"RUFF",
0.06020310364795,
0.060783660589803,
"#FFFFFF",
0
],
[
"OST",
0.053142581554735,
0.053661051379115,
"#FFF8F8",
0.029021159105028
],...
]
}
}
Trendlines
We use advanced pattern detection AI algorithms to automatically determine trendlines for all coins.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/prices_trendlines \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Support and resistance levels are computed from price bands (from our dashboard):
curl "http://bittsanalytics.com/bittsanalytics/api3.php/prices_trendlines" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"prices_trendlines": {
"columns": [
"ticker",
"datum_start",
"price_start",
"datum_end",
"price_end",
"type_of_extreme",
"alert"
],
"records": [
[
"ZRX",
"2021-09-22 00:00:00",
0.859215,
"2021-11-03 00:00:00",
"0.7817550000000001",
"minimum",
0
],
[
"ZRX",
"2021-10-03 00:00:00",
1,
"2021-11-03 00:00:00",
"1.4428571428571433",
"maximum",
0
],
[
"ZIL",
"2021-09-22 00:00:00",
0.084,
"2021-11-03 00:00:00",
"0.058188000000000004",
"minimum",
0
],
[
"ZIL",
"2021-10-03 00:00:00",
0.102006,
"2021-11-03 00:00:00",
"0.11798133333333333",
"maximum",
1
],
[
"ZEN",
"2021-10-06 00:00:00",
75.05,
"2021-11-03 00:00:00",
"61.570000000000036",
"minimum",
0
],
[
"ZEC",
"2021-09-29 00:00:00",
105.78,
"2021-11-03 00:00:00",
"131.48000000000002",
"minimum",
0
],...
]
}
}
Historical bull and bear markets / cycles
We provide you with all historical bull and bear markets for all coins individually. See which bull markets were most profitable and which bear markets were the worst.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/bull_bear_markets1 \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
Example chart of Bitcoin bull and bear markets generated from our API data:
curl "http://bittsanalytics.com/bittsanalytics/api3.php/bull_bear_markets1" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
The above command returns JSON structured like this:
{
"bull_bear_markets1": {
"columns": [
"ticker",
"datum",
"startDate",
"endDate",
"mcnr",
"startPrice",
"endPrice"
],
"records": [
[
"btc",
"2013-04-28",
"2013-04-28",
"2013-04-29",
0.049223946784922,
135.3,
141.96
],
[
"btc",
"2013-04-29",
"2013-04-29",
"2013-05-03",
-0.35890391659622,
141.96,
91.01
],
[
"btc",
"2013-05-03",
"2013-05-03",
"2013-05-26",
0.47895835622459,
91.01,
134.6
],
[
"btc",
"2013-05-26",
"2013-05-26",
"2013-07-06",
-0.49621842496285,
134.6,
67.809
],
[
"btc",
"2013-07-06",
"2013-07-06",
"2013-11-30",
15.626848943356,
67.809,
1127.45
],
[
"btc",
"2013-11-30",
"2013-11-30",
"2013-12-18",
-0.50387156858397,
1127.45,
559.36
],
[
"btc",
"2013-12-18",
"2013-12-18",
"2014-01-06",
0.67402030892449,
559.36,
936.38
],
[
"btc",
"2014-01-06",
"2014-01-06",
"2014-02-25",
-0.47744505435827,
936.38,
489.31
],
[
"btc",
"2014-02-25",
"2014-02-25",
"2014-03-04",
0.3794935725818,
489.31,
675
],
[
"btc",
"2014-03-04",
"2014-03-04",
"2014-04-10",
-0.46542118518519,
675,
360.8407
],
[
"btc",
"2014-04-10",
"2014-04-10",
"2014-06-03",
0.84948177963295,
360.8407,
667.3683
],
[
"btc",
"2014-06-03",
"2014-06-03",
"2015-01-14",
-0.74204962986705,
667.3683,
172.1479
],
[
"btc",
"2015-01-14",
"2015-01-14",
"2017-06-11",
16.506538273194,
172.1479,
3013.7138
],
[
"btc",
"2017-06-11",
"2017-06-11",
"2017-07-16",
-0.36055671058704,
3013.7138,
1927.0990656212
],
[
"btc",
"2017-07-16",
"2017-07-16",
"2017-09-01",
1.523582277342,
1927.0990656212,
4863.1930486841
],
[
"btc",
"2017-09-01",
"2017-09-01",
"2017-09-14",
-0.36242133025275,
4863.1930486841,
3100.668154704
],
[
"btc",
"2017-09-14",
"2017-09-14",
"2017-12-16",
5.3423088012198,
3100.668154704,
19665.394927242
],
[
"btc",
"2017-12-16",
"2017-12-16",
"2018-02-06",
-0.65156800939588,
19665.394927242,
6852.0527005149
],
[
"btc",
"2018-02-06",
"2018-02-06",
"2018-03-06",
0.68218509606974,
6852.0527005149,
11526.420930291
],
[
"btc",
"2018-03-06",
"2018-03-06",
"2018-04-07",
-0.42490782733464,
11526.420930291,
6628.7544558563
],
[
"btc",
"2018-04-07",
"2018-04-07",
"2018-05-06",
0.47331516810986,
6628.7544558563,
9766.2444854889
],
[
"btc",
"2018-05-06",
"2018-05-06",
"2018-06-29",
-0.39792732169022,
9766.2444854889,
5879.9889744064
],
[
"btc",
"2018-06-29",
"2018-06-29",
"2018-07-25",
0.43237920343238,
5879.9889744064,
8422.3739233515
],
[
"btc",
"2018-07-25",
"2018-07-25",
"2018-12-15",
-0.61808544963912,
8422.3739233515,
3216.6271499079
],....
]
}
}
Investor Sentiment Index and Investor Social Buzz Index
Investor Sentiment Index and Investor Social Buzz Index are based on evaluation of only those 1+ million tweets that we analyse each day that were published by authors that we identified as investors and/or traders.
User is identified as investor/trader if profile description contains words like 'investor', 'trader', 'hedge fund', 'investing' and others.
From these posts we compute on hourly basis the average sentiment (Investor Sentiment Index) and total mentions buzz (Investor Social Buzz Index).
We believe these Investor Indices give an unique insight in the social activity and opinions of investors/traders in the crypto community.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
GET http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h?filter[]=valuta,eq,Investor Trader Index" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h?filter[]=valuta,eq,Investor Trader Index" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Example of historical chart for BittsAnalytics Investor Sentiment Index:
Example of current value of BittsAnalytics Investor Social Buzz Index:
The above command returns JSON structured like this (sentiment index):
{
"crypto_indices_sentiment_h": {
"columns": [
"valuta",
"datum",
"index"
],
"records": [
[
"Investor Trader Index",
"2022-01-02 00:00:00",
"0.19868"
],
[
"Investor Trader Index",
"2022-01-02 01:00:00",
"0.27018"
],
[
"Investor Trader Index",
"2022-01-02 02:00:00",
"0.18843"
],
[
"Investor Trader Index",
"2022-01-02 03:00:00",
"0.25520"
],
[
"Investor Trader Index",
"2022-01-02 04:00:00",
"0.26389"
],
[
"Investor Trader Index",
"2022-01-02 05:00:00",
"0.11613"
],
[
"Investor Trader Index",
"2022-01-02 06:00:00",
"0.35582"
],
[
"Investor Trader Index",
"2022-01-02 07:00:00",
"0.21991"
],.....
]
}
}
Influencer sentiment and social buzz indices
Our influencer indices are computed by segmenting social media tweets depending on the number of followers of the author, we distinguish between 3 group of authors:
- small following social media users - those that have less than 100 followers
- medium following social media users - those between 100 and 1000 followers
- large following social media users - those with more than 1000 followers
We then compute average sentiment and number of mentions from social media posts of each group of users, resulting in three sets of indices.
HTTP Request
GET http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
GET http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h \ -H "x-api-key:b4dcde2ce5fb2d0b887b5"
Query Parameters
| Parameter | Type | Description |
|---|---|---|
| exclude | string | One or more related entities (comma separated). |
| include | string | One or more related entities (comma separated). |
| order | string | Column you want to sort on and the sort direction (comma separated). Example: id,desc. |
| page | string | One or more related entities (comma separated). |
| transform | boolean | One or more related entities (comma separated). |
| columns | string | One or more related entities (comma separated). |
| filter[] | array of strings | One or more related entities (comma separated). |
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h?filter[]=valuta,eq,Small Following Index (<100)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h?filter[]=valuta,eq,Small Following Index (<100)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h?filter[]=valuta,eq,Medium Following Index (100-1000)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h?filter[]=valuta,eq,Medium Following Index (100-1000)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_sentiment_h?filter[]=valuta,eq,Large Following Index (>1000)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
curl "http://bittsanalytics.com/bittsanalytics/api3.php/crypto_indices_volume_h?filter[]=valuta,eq,Large Following Index (>1000)" \ -H "x-api-key:b4dcde2ce5fb2d0b88"
Example of historical chart for BittsAnalytics Influencer Sentiment Indices:
Example of current value of BittsAnalytics Influencer Social Buzz Indices:
The above command returns JSON structured like this (sentiment index):
{
"crypto_indices_sentiment_h": {
"columns": [
"valuta",
"datum",
"index"
],
"records": [
[
"Large Following Index (>1000)",
"2022-01-02 00:00:00",
"0.20710"
],
[
"Large Following Index (>1000)",
"2022-01-02 01:00:00",
"0.23623"
],
[
"Large Following Index (>1000)",
"2022-01-02 02:00:00",
"0.19566"
],
[
"Large Following Index (>1000)",
"2022-01-02 03:00:00",
"0.20876"
],
[
"Large Following Index (>1000)",
"2022-01-02 04:00:00",
"0.14413"
],
[
"Large Following Index (>1000)",
"2022-01-02 05:00:00",
"0.15315"
],
[
"Large Following Index (>1000)",
"2022-01-02 06:00:00",
"0.18832"
],
[
"Large Following Index (>1000)",
"2022-01-02 07:00:00",
"0.13362"
],
[
"Large Following Index (>1000)",
"2022-01-02 08:00:00",
"0.22896"
],
[
"Large Following Index (>1000)",
"2022-01-02 09:00:00",
"0.14181"
],
[
"Large Following Index (>1000)",
"2022-01-02 10:00:00",
"0.11224"
],
[
"Large Following Index (>1000)",
"2022-01-02 11:00:00",
"0.19903"
],.....
]
}
}
Errors
The BittsAnalytics API uses the following error codes:
| Error Code | Meaning |
|---|---|
| 400 | Bad Request -- Your request is invalid. |
| 401 | Unauthorized -- Your API key is wrong. |
| 406 | Not Acceptable -- You requested a format that isn't json. |
| 429 | Too Many Requests |
| 500 | Internal Server Error -- We had a problem with our server. Try again later. |
| 503 | Service Unavailable -- We're temporarily offline for maintenance. Please try again later. |
- For OCR recognition we use OCR API solution for all your document needs.
- For website categorization we use Restful API for classifying URLs, with JSON output.
- For reverse IP lookup API we use the API to get domain reverse lookup results.