Get Sentiment History
Attributes
API Request
Example Request with cURL
curl \
--request GET \
--url 'https://data.guavy.com/api/v1/sentiment/get-sentiment-history/<symbol>?limit=<integer>' \
--header 'Authorization: Bearer YOUR-GUAVY-ACCESS-TOKEN' \
--header 'Content-Type: application/json'
This request format works across all modern HTTP clients, including Python requests, JavaScript fetch, and other programming language libraries.
Example Response for /api/v1/sentiment/get-sentiment-history/btc?limit=2
{
"sentiment": [
{
"date": "2025-12-13",
"negative": 137,
"neutral": 0,
"positive": 197,
"symbol": "BTC",
"timestamp": 1765609200000,
"total": 334
},
{
"date": "2025-12-12",
"negative": 422,
"neutral": 1,
"positive": 579,
"symbol": "BTC",
"timestamp": 1765522800000,
"total": 1002
}
]
}
Response Object
API Limits
The Guavy API has a limit of 10 simultaneous connections. You'll receive a 429 error if you reach the limit. At exceptionally high volumes, you may receive an HTTP 429 or 403 without a JSON body.
We recommend that you cache frequently accessed values that do not change often in your application's data store. This will prevent your application from bumping up against the throttling limitations and will likely provide faster access to that data.
Account Limits
Your Guavy account will typically have a licensed limit of at least 100,000 API calls per month. In addition, there is a limit of 10,000 API calls per day. If you reach these limits, you will receive a 429 error.
Connection Timeouts
The Guavy API has a 120-second timeout on API calls. You may see this type of timeout after you've made a network socket connection and are already sending and receiving data. Response times are dependent on the complexity of your request and the general load across Guavy. Some endpoints in the Guavy API return values that are large and slow to calculate.
