The endpoint#

GET /v1/cache/purge-logs returns the same records with date filters applied, scoped to the authenticated tenant exactly like the dashboard. The list returns up to 100 rows per request.

Pair it with the purge API#

Purges created through the delivery purge API land here as Service API rows, so a pipeline can purge and then verify its own footprint in one loop — the automation equivalent of Confirming a purge.

Authentication#

Use a service account token so the actor column attributes purges to Service API rather than a person; see Authenticating requests.

Why there is no screenshot here#

This step documents an API response rather than a screen. The dashboard rows it mirrors are pictured in Read an entry.

Limits worth designing around#

Responses are capped at 100 rows per request and are tenant-scoped exactly like the dashboard, so a scheduled report should page with date filters rather than fetching everything at once.