Stops monitoring a profile: no further scheduled refresh crawls are charged for it. Free to call. Pass the internal profileId (from list_tracked_profiles or search results). The profile and its already-crawled posts stay in the database and searchable; only the recurring refresh stops. Returns not_found if the profile is not currently being monitored.
Cancel the scheduled refresh crawls for a profile you no longer need kept fresh. It is the off switch for track_profile: free to call, immediate, and non-destructive. The profile and everything already crawled stay in the database and searchable, only the recurring, credit-spending refresh stops.
DELETE /api/v1/tracking. Authenticate with your API key. Same call in three languages:
cURL
curl -X DELETE "https://viraloutliers.com/api/v1/tracking" \
-H "Authorization: Bearer so_live_YOUR_KEY"Python (requests)
import requests
r = requests.delete(
"https://viraloutliers.com/api/v1/tracking",
headers={"Authorization": "Bearer so_live_YOUR_KEY"},
)
print(r.json())JavaScript (fetch)
const res = await fetch("https://viraloutliers.com/api/v1/tracking", {
method: "DELETE",
headers: { "Authorization": "Bearer so_live_YOUR_KEY" },
});
const data = await res.json();
console.log(data);| Name | Type | Description |
|---|---|---|
profileId* | string | Internal profile id to stop monitoring (query ?profileId= or JSON body). |
Given the internal profileId, it ends monitoring so no further scheduled refresh crawls are charged for that account. It is free, and it returns not_found if the profile is not currently being monitored, so it is safe to call defensively.
Untracking is not deletion. The profile and all of its already-crawled posts and stats remain in the database and keep appearing in search and get_profile. You are cancelling a subscription-like refresh, not removing data, and you can re-track the profile later to resume refreshes.
Use it for budget control: list_tracked_profiles to see what is being refreshed and what it is costing, then untrack the accounts you no longer need kept current to cut recurring credit spend. It is the natural cleanup step when a campaign ends or a competitor stops mattering.
Because it only stops future refreshes and leaves the data intact, there is no downside to untracking an account you are done monitoring: you keep the history you paid for and stop paying for updates you do not need.
This skill is free and never spends credits.
Call untrack_profile with the profile id. It is free and immediate: no further refresh crawls are charged. The profile stays in the database and remains searchable; you are just cancelling the recurring refresh, not deleting the data.
No. Untracking only stops the scheduled refresh crawls. Every post and stat already crawled stays in the database and keeps showing up in search and get_profile; you can re-track the profile later to resume refreshes.
The call returns not_found rather than erroring, so it is safe to call even when you are not sure a profile is currently tracked. Nothing is charged and nothing is deleted, which makes untrack_profile safe to run defensively in cleanup routines.
Also available as an MCP tool.
Related topics: cancel scheduled crawl · manage monitored profiles · API credit budgeting · stop recurring profile refresh