This endpoint provides the data to power “Recommendations” charts and tables in the Analysis section.
Asset Type Compatibility
- Stocks: The endpoint is designed primarily for stocks.
- ETFs and Mutual funds: The request can be executed via the unified symbol universe, but results may be empty due to data availability and asset nature.
When to Use This Endpoint
- Show analyst recommendation breakdown for a ticker over time.
- Build a “Recommendations” chart or table with historical snapshots.
- Track changes in sentiment across Strong Buy / Buy / Hold / Sell / Strong Sell.
- Filter tickers based on recommendation composition (e.g., high Strong Buy, low Sell).
Request Parameters
v1/analysis/recommendations
Asset identifier (ticker symbol).
Date range filter (YYYY-MM-DD).
Date range filter (YYYY-MM-DD).
Maximum number of items to return (user-defined).
Pagination offset (0-based).
Optional filter expressions.
Each filter condition is defined as: [field, operator, value]. Conditions can be combined using logical operators and/or.
Supported operators:
Numeric fields:
>- greater than>=- greater than or equal<- less than<=- less than or equal=- equals<>- not equal
String fields:
like– pattern match (requires % as a wildcard)not_like- pattern does not match (requires % as a wildcard)contains- value exists in stringnot_contains- value does not exist in stringstartswith- string starts with valueendswith- string ends with value
% usage examples:
- %abc% - matches any string containing "abc"
- abc% - matches any string starting with "abc"
- %abc - matches any string ending with "abc"
Example:
"filters": [
["buy", "=", 24],
"and",
["hold", "<>", 10]
]Optional sorting configuration for result items. Each sorting setup is defined as [selector, desc]:
selector- Metric used for sorting (e.g., date).desc- Sorting direction (true for descending, false for ascending).
Sortings can be combined using ,.
Example:
"sort_by": [
{
"selector": "date",
"desc": true
}
]User-defined identifier for the task (max 255 characters).
It is returned in the response data object, allowing you to match results with the corresponding request. It does not affect API processing or filtering logic.
curl --location "https://api.finimpulse.com/v1/analysis/recommendations" \
--header "Content-Type: application/json" \
--header "Authorization: Bearer <API_TOKEN>" \
-d '{
"symbol": "AAPL",
"start_date": "2025-01-01",
"end_date": "2026-01-30",
"limit": 3,
"offset": 0,
"tag": "just tag"
}'
using System.Net.Http;
using System.Net.Http.Headers;
using System.Text;
var client = new HttpClient();
var url = "https://api.finimpulse.com/v1/analysis/recommendations";
client.DefaultRequestHeaders.Authorization = new AuthenticationHeaderValue("Bearer", "<API_TOKEN>");
client.DefaultRequestHeaders.Accept.Add(new MediaTypeWithQualityHeaderValue("application/json"));
var json = @"{
""symbol"": ""AAPL"",
""start_date"": ""2025-01-01"",
""end_date"": ""2026-01-30"",
""limit"": 3,
""offset"": 0,
""tag"": ""just tag""
}";
var content = new StringContent(json, Encoding.UTF8, "application/json");
var response = await client.PostAsync(url, content);
var result = await response.Content.ReadAsStringAsync();
Console.WriteLine(result);
<?php
$curl = curl_init();
curl_setopt_array($curl, [
CURLOPT_URL => "https://api.finimpulse.com/v1/analysis/recommendations",
CURLOPT_RETURNTRANSFER => true,
CURLOPT_CUSTOMREQUEST => "POST",
CURLOPT_HTTPHEADER => [
"Content-Type: application/json",
"Authorization: Bearer <API_TOKEN>"
],
CURLOPT_POSTFIELDS => json_encode(
[
"symbol" => "AAPL",
"start_date" => "2025-01-01",
"end_date" => "2026-01-30",
"limit" => 3,
"offset" => 0,
"tag" => "just tag"
]
)
]);
$response = curl_exec($curl);
curl_close($curl);
echo $response;
import urllib.request
import json
url = "https://api.finimpulse.com/v1/analysis/recommendations"
headers = {
"Content-Type": "application/json",
"Authorization": "Bearer <API_TOKEN>"
}
data = {
"symbol": "AAPL",
"start_date": "2025-01-01",
"end_date": "2026-01-30",
"limit": 3,
"offset": 0,
"tag": "just tag"
}
req = urllib.request.Request(url,
data=json.dumps(data).encode("utf-8"),
headers=headers,
method="POST")
with urllib.request.urlopen(req) as response:
result = json.loads(response.read().decode("utf-8"))
print(result)
const https = require('https');
const data = JSON.stringify({
"symbol": "AAPL",
"start_date": "2025-01-01",
"end_date": "2026-01-30",
"limit": 3,
"offset": 0,
"tag": "just tag"
});
const options = {
method: 'POST',
headers: {
'Content-Type': 'application/json',
'Authorization': 'Bearer <API_TOKEN>',
'Content-Length': Buffer.byteLength(data)
}
};
const req = https.request('https://api.finimpulse.com/v1/analysis/recommendations', options, (res) => {
let body = '';
res.on('data', chunk => body += chunk);
res.on('end', () => console.log(JSON.stringify(JSON.parse(body), null, 2)));
});
req.on('error', (e) => console.error(e));
req.write(data);
req.end();
Response
The response contains pagination fields and a list of recommendation snapshot records.
Pagination Fields
Total number of matching records available.
Number of records returned in the current response.
Array of recommendation snapshot records.
Recommendation Item Fields
Snapshot date (YYYY-MM-DD).
Number of Strong Buy recommendations.
Number of Buy recommendations.
Number of Hold recommendations.
Number of Sell recommendations.
Number of Strong Sell recommendations.
{
"task_id": "7391d91a-84f1-483c-b949-98ae05809663",
"status_code": 20000,
"status_message": "OK",
"cost": 0,
"data": {
"symbol": "AAPL",
"limit": 3,
"offset": 0,
"filters": [
[
"buy",
"=",
24
],
"and",
[
"hold",
"<>",
10
]
],
"start_date": "2025-01-01",
"end_date": "2026-01-30",
"sort_by": [
{
"selector": "date",
"desc": true
}
]
},
"result": {
"total_count": 3,
"items_count": 3,
"items": [
{
"date": "2025-12-01",
"strong_buy": 5,
"buy": 24,
"hold": 15,
"sell": 1,
"strong_sell": 3
},
{
"date": "2025-11-01",
"strong_buy": 5,
"buy": 24,
"hold": 15,
"sell": 1,
"strong_sell": 3
},
{
"date": "2025-10-01",
"strong_buy": 5,
"buy": 24,
"hold": 15,
"sell": 1,
"strong_sell": 3
}
]
}
}Notes
- Recommendation values are counts (number of analysts), not percentages.
- Records are typically returned as periodic snapshots (often monthly), depending on provider coverage.
