Takedown feed

Follow the ads and advertisers AdLib deleted after a takedown or erasure request, so you can remove your own copies.

Rights holders and people shown in ads can ask us to delete an ad, an advertiser or a media file (how). Deleting it on our side doesn't reach copies you stored. GET /v1/erasures lists what we deleted, so you can remove those copies too. The same list is in your dashboard.

The feed is free. It shows what was deleted and when, but never who asked or why.

Poll the feed

Shell

curl "https://api.adlibapi.com/v1/erasures?limit=100" \
  -H "X-API-Key: $ADLIB_API_KEY"

JSON

{
  "data": [
    {
      "id": "meta:1037130442034659",
      "kind": "ad",
      "erased_at": "2026-11-04T09:30:00Z",
      "media_sha256": ["e3b150351504c43e37541b89b4b0a03f62..."]
    }
  ],
  "next_cursor": "42"
}

Entries come oldest first. Store next_cursor and pass it as cursor on your next poll: you get what was added since. next_cursor is also set when a page is empty, so you can always keep the latest one. since starts from a point in time instead, and limit takes up to 500.

Field	Meaning
`id`	The deleted ad, or with `kind: advertiser` the advertiser and all its ads
`erased_at`	When we deleted it
`media_sha256`	Files deleted with it. They match the `sha256` on the media entries you received

What to remove

Match your copies by id and by media_sha256. A file that other ads still use stays in our archive and isn't listed, so an ad's entry can have fewer files than the ad had.

Media links of a deleted ad answer 404. Browsers may keep a redirect for up to a day.