Fetch news for a monitor
curl --request POST \
--url https://api.itoflow.ai/watchlists/{id}/news/fetch \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.itoflow.ai/watchlists/{id}/news/fetch"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.itoflow.ai/watchlists/{id}/news/fetch', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"queued": 4503599627370495,
"subjects": 4503599627370495
}{
"error": "INVALID_REQUEST",
"message": "<string>"
}Monitors
Fetch news for a monitor
Asks Itoflow to judge the last 24 hours of news for a monitor’s subjects that are behind: the companies it holds and its mandate. It returns at once; judging runs in the background, usually within a few minutes. Then call getMonitorNews every few seconds until feed.coverage.current equals feed.coverage.subjects. A paused monitor fetches too. Calling again while judging runs is safe: a subject being judged is skipped, and one judged since is not judged again. A missing monitor, one you do not own, and one being deleted all return the same 404.
Operation ID: fetchMonitorNews.
POST
https://api.itoflow.ai
/
watchlists
/
{id}
/
news
/
fetch
Fetch news for a monitor
curl --request POST \
--url https://api.itoflow.ai/watchlists/{id}/news/fetch \
--header 'Authorization: Bearer <token>'import requests
url = "https://api.itoflow.ai/watchlists/{id}/news/fetch"
headers = {"Authorization": "Bearer <token>"}
response = requests.post(url, headers=headers)
print(response.text)const options = {method: 'POST', headers: {Authorization: 'Bearer <token>'}};
fetch('https://api.itoflow.ai/watchlists/{id}/news/fetch', options)
.then(res => res.json())
.then(res => console.log(res))
.catch(err => console.error(err));{
"queued": 4503599627370495,
"subjects": 4503599627370495
}{
"error": "INVALID_REQUEST",
"message": "<string>"
}