Hey @RArroyo
Yes — the supported replacement is the Task Management “task status list” endpoint, filtered down to Cloud Account Aggregation tasks with an ERROR/TEMPERROR/TERMINATED completion status.
In other words: instead of older “cc/api/org/…” style endpoints , you query /task-status and filter by type + completionStatus.
What to use
GET /v2026/task-status (or /v2025/task-status depending on what your tenant exposes) with:
-
filters=type eq "Cloud Account Aggregation" and completionStatus in ("ERROR","TEMPERROR","TERMINATED") -
optional
and sourceId eq "<SOURCE_ID>"to narrow to a specific source -
sorters=-createdto see newest failures first -
limit/offsetfor paging
In v2026 docs this endpoint is marked experimental and requires
X-SailPoint-Experimental: true. It also only returns tasks from the last 90 days. SailPoint Developer Community
example (all failed source account aggregations)
curl --request GET \
--url 'https://<tenant>.api.identitynow.com/v2026/task-status?limit=250&offset=0&sorters=-created&filters=type%20eq%20%22Cloud%20Account%20Aggregation%22%20and%20completionStatus%20in%20(%22ERROR%22,%22TEMPERROR%22,%22TERMINATED%22)' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json' \
--header 'X-SailPoint-Experimental: true'
example (failed account aggregations for one source)
curl --request GET \
--url 'https://<tenant>.api.identitynow.com/v2026/task-status?limit=250&offset=0&sorters=-created&filters=type%20eq%20%22Cloud%20Account%20Aggregation%22%20and%20sourceId%20eq%20%22<SOURCE_ID>%22%20and%20completionStatus%20in%20(%22ERROR%22,%22TEMPERROR%22,%22TERMINATED%22)' \
--header 'Authorization: Bearer <ACCESS_TOKEN>' \
--header 'Accept: application/json' \
--header 'X-SailPoint-Experimental: true'
Quick notes that help
-
Pending/running aggregations: use
completionStatus isnull(same pattern SailPoint calls out when deprecating the older “pending tasks” endpoint). -
Completion statuses are standardized (so you can reliably filter):
SUCCESS,WARNING,ERROR,TERMINATED,TEMPERROR. -
Filter operator syntax (
in (…),isnull,and, etc.) is documented under Standard Collection Parameters. -
If you need history beyond 90 days, you’ll have to poll and store these results externally (because the endpoint won’t return older task records)
Sources you may like to refer too also
-
SailPoint Developer Docs — Retrieve task status list (
/task-status, 90-day retention, experimental header) SailPoint Developer Community -
SailPoint Developer Docs — Deprecated pending tasks guidance (use
/task-statuswithcompletionStatus isnull) SailPoint Developer Community -
SailPoint Developer Docs — TaskStatus model (valid
completionStatusenum values) SailPoint Developer Community
Excellent. Thank you so much Amr.
You welcome any happy that help