# Deleted Post Viewer - See What They Took Down (`reapx/deleted-content-archive`) Actor

See what they took down. Posts kept on the record while they are still live, so when a creator quietly deletes the one that mattered, you still have it - text, media and all.

- **URL**: https://apify.com/reapx/deleted-content-archive.md
- **Developed by:** [Tarek Etman](https://apify.com/reapx) (community)
- **Categories:** For creators, Social media, Marketing
- **Stats:** 2 total users, 1 monthly users, 100.0% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

$0.75 / 1,000 deleted content archive item collecteds

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.

Learn more: https://docs.apify.com/platform/actors/running/actors-in-store#pay-per-event

## What's an Apify Actor?

Actors are web data automations that power AI and operations. They run on the Apify platform to scrape websites, process data, connect APIs, and automate workflows.
In Batch mode, an Actor accepts a well-defined JSON input, performs an action which can take anything from a few seconds to a few hours,
and optionally produces a well-defined JSON output, datasets with results, or files in key-value store.
In Standby mode, an Actor provides a web server which can be used as a website, API, or an MCP server.
Actors are written with capital "A".

## How to integrate an Actor?

If asked about integration, you help developers integrate Actors into their projects.
You adapt to their stack and deliver integrations that are safe, well-documented, and production-ready.
The best way to integrate Actors is as follows.

- **AI agents and MCP clients** — the [Apify MCP server](https://docs.apify.com/integrations/mcp.md) at `https://mcp.apify.com` (remote, streamable HTTP, OAuth on first use).
- **Agentic workflows and local Actor development** — [Agent Skills](https://apify.com/.well-known/agent-skills/index.json) with the [Apify CLI](https://docs.apify.com/cli/docs.md): `npm install -g apify-cli`, then `apify login`.
- **JavaScript/TypeScript projects** — the official [JS/TS client](https://docs.apify.com/api/client/js/docs.md): `npm install apify-client`.
- **Python projects** — the official [Python client](https://docs.apify.com/api/client/python/docs.md): `pip install apify-client`.
- **Any other language** — the [REST API](https://docs.apify.com/api/v2.md).

For usage examples, see the [API](#api) section below.

For more details, see Apify documentation as [Markdown index](https://docs.apify.com/llms.txt) and [Markdown full-text](https://docs.apify.com/llms-full.txt).

# README

![reapX - the record of what changed](https://reapx.dev/reapx.gif)

## Deleted Content Archive - What Disappeared, And When

> *"The post we need for the dispute was deleted. Is it just gone?"*

Yes, unless someone recorded it while it was live. You cannot scrape the past retroactively once content has been removed from social platforms.

The Deleted Content Archive captures social media posts while they are live, preserving captions, media links, metadata, and engagement history. When posts are later edited, privated, or deleted, the archive retains the original record.

***

### ⬇️ Input

Set target post or profile URL to archive and monitor.

```json
{
  "url": "https://www.instagram.com/nasa/"
}
```

***

### ⬆️ Output

Each output record emits structured post data, timestamp verification, and deletion status:

- `entityId`: Unique canonical identifier for the monitored post or profile.
- `stillLive`: Boolean status indicating if the content remains active.
- `deletedAt`: Timestamp when content removal was detected.
- `changedFields`: List of properties modified since initial capture.
- `daysTracked`: History depth in days.

***

### How it works

1. Captures live post content, media attachments, and metadata upon initial run.
2. Compares subsequent observations against stored baseline records.
3. Detects deleted posts, modified captions, or privated accounts.
4. Emits verified change logs.

***

### ❓ FAQ

**Can deleted content be recovered retroactively?**
No. Content must be captured while active to preserve its record.

**Does this require account credentials?**
No. It operates entirely on publicly visible content without requiring login tokens.

***

### 💬 Your feedback

Need custom archiving schedules or enterprise export integration? Contact reapxdev@proton.me or visit reapx.dev.

***

*Unofficial - not affiliated with third parties. Collects only data visible without logging in.*
reapx · reapx.dev · reapxdev@proton.me

# Actor input Schema

## `url` (type: `string`):

Paste the link to the post or profile you want on the record. We keep what is there now, so if it disappears later you still have it - text, media and all.

## `proxyConfiguration` (type: `object`):

How the run reaches the platform. The default is already the route that works for this source, so leave it alone unless you have a reason to change it.

## Actor input object example

```json
{
  "url": "https://www.instagram.com/nasa/",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}
```

# Actor output Schema

## `items` (type: `string`):

No description

# API

You can run this Actor programmatically using our API. Below are code examples in JavaScript, Python, and CLI, as well as the OpenAPI specification and MCP server setup.

## JavaScript example

```javascript
import { ApifyClient } from 'apify-client';

// Initialize the ApifyClient with your Apify API token
// Replace the '<YOUR_API_TOKEN>' with your token
const client = new ApifyClient({
    token: '<YOUR_API_TOKEN>',
});

// Prepare Actor input
const input = {
    "url": "https://www.instagram.com/nasa/",
    "proxyConfiguration": {
        "useApifyProxy": true,
        "apifyProxyGroups": [
            "RESIDENTIAL"
        ]
    }
};

// Run the Actor and wait for it to finish
const run = await client.actor("reapx/deleted-content-archive").call(input);

// Fetch and print Actor results from the run's dataset (if any)
console.log('Results from dataset');
console.log(`💾 Check your data here: https://console.apify.com/storage/datasets/${run.defaultDatasetId}`);
const { items } = await client.dataset(run.defaultDatasetId).listItems();
items.forEach((item) => {
    console.dir(item);
});

// 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/js/docs

```

## Python example

```python
from apify_client import ApifyClient

# Initialize the ApifyClient with your Apify API token
# Replace '<YOUR_API_TOKEN>' with your token.
client = ApifyClient("<YOUR_API_TOKEN>")

# Prepare the Actor input
run_input = {
    "url": "https://www.instagram.com/nasa/",
    "proxyConfiguration": {
        "useApifyProxy": True,
        "apifyProxyGroups": ["RESIDENTIAL"],
    },
}

# Run the Actor and wait for it to finish
run = client.actor("reapx/deleted-content-archive").call(run_input=run_input)

# Fetch and print Actor results from the run's dataset (if there are any)
print("💾 Check your data here: https://console.apify.com/storage/datasets/" + run["defaultDatasetId"])
for item in client.dataset(run["defaultDatasetId"]).iterate_items():
    print(item)

# 📚 Want to learn more 📖? Go to → https://docs.apify.com/api/client/python/docs/quick-start

```

## CLI example

```bash
echo '{
  "url": "https://www.instagram.com/nasa/",
  "proxyConfiguration": {
    "useApifyProxy": true,
    "apifyProxyGroups": [
      "RESIDENTIAL"
    ]
  }
}' |
apify call reapx/deleted-content-archive --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "command": "npx",
            "args": [
                "mcp-remote",
                "https://mcp.apify.com/?tools=reapx/deleted-content-archive",
                "--header",
                "Authorization: Bearer <YOUR_API_TOKEN>"
            ]
        }
    }
}

```

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/8XwyM3V3Ase7IqnPH/builds/faqkzubtSonIcXsiK/openapi.json