Retour à toutes les discussions
[:authors_rating_pro] is not a valid field for Screeners::Search.
steinar.talmoen
vor 2 Jahren
Stopped working a couple of days ago, example for endpoint still shows authors_rating_pro…
const options = {
method: ‘POST’,
url: ‘https://seeking-alpha.p.rapidapi.com/screeners/get-results’,
params: {page: ‘1’, per_page: ‘100’},
headers: {
‘content-type’: ‘application/json’,
‘X-RapidAPI-Host’: ‘seeking-alpha.p.rapidapi.com’
},
data: ‘{“quant_rating”:{“gte”:3.5,“lte”:5},“authors_rating_pro”:{“gte”:3.5,“lte”:5},“sell_side_rating”:{“gte”:3.5,“lte”:5},“value_category”:{“gte”:1,“lte”:6},“growth_category”:{“gte”:1,“lte”:6},“profitability_category”:{“gte”:1,“lte”:6},“momentum_category”:{“gte”:1,“lte”:6},“eps_revisions_category”:{“gte”:1,“lte”:6}}’
};
Participez à la discussion - ajoutez un commentaire ci-dessous:
Connectez-vous / Inscrivez-vous pour publier de nouveaux commentaires
The work around is to replace “authors_rating_pro” with “authors_rating”:
.replace(’“authors_rating_pro”’,’“authors_rating”’)
Can we ask the api developers to change the api ‘screeners/get-results’ to match this change in the api to match the system.
Regards
Hello,
All of our APIs provide live data so if the official developers make some changes to the system of Seeking Alpha, the endpoints may be affected on real time. You should always use …/screener-filters/list endpoint to get the correct id first.
Regards.
The workaround is no longer required for ‘marketcap_display’, I’m quessing a fix was made to the api.
Some mismatch is now in place where the api:
"https://seeking-alpha.p.rapidapi.com/screeners/list"
returns fields:
Top Rated Stocks,{“quant_rating”: {“gte”: 3.5, “lte”: 5.0}, “authors_rating_pro”: {“gte”: 3.5, “lte”: 5.0}, “sell_side_rating”: {“gte”: …
The do not match the fields in:
"https://seeking-alpha.p.rapidapi.com/screeners/get-results"
Can I see what has change?
Hello,
You are interested in the discussion at https://rapidapi.com/apidojo/api/seeking-alpha/discussions/28423
Regards.