# Snapchat Account Age Checker and Last Activity Time (`karamelo/snapchat-account-age-checker-and-last-activity`) Actor

Collect public Snapchat profile creation date, identity, followers, and recent activity details.

- **URL**: https://apify.com/karamelo/snapchat-account-age-checker-and-last-activity.md
- **Developed by:** [karamelo](https://apify.com/karamelo) (community)
- **Stats:** 34 total users, 3 monthly users, 98.2% runs succeeded, 0 bookmarks
- **User rating**: No ratings yet

## Pricing

from $2.10 / 1,000 results

This Actor is paid per event. You are not charged for the Apify platform usage, but only a fixed price for specific events.
Since this Actor supports Apify Store discounts, the price gets lower the higher subscription plan you have.

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

## What's an Apify Actor?

An Actor is a serverless cloud program that runs on the Apify platform. It has two run modes.
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.

Apify vocabulary and the platform model are defined once, in the agent quickstart at https://apify.com/agents.md.

## 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.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For examples already wired to this Actor's own input schema, see the [API](#api) section below.

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).

# README

### What does Snapchat Account Age Checker and Last Activity do?

Snapchat Account Age Checker and Last Activity turns a list of public Snapchat usernames into structured profile records. It is designed for users who need consistent fields for profile research, account cataloging, creator discovery, reporting, or data-quality reviews. Enter one or more usernames and receive a dataset row for every profile with the required public details available.

Each successful row includes the public username, display name, avatar URL when available, a complete numeric follower count when available, the account creation month and year, calculated account age, and the latest available activity date. It also includes `date_created` in `DD-MM-YYYY` form without a time component.

The Actor accepts usernames with or without the leading `@` and handles three profiles at a time by default. Increase concurrency only after reviewing a small first result set and confirming that the returned fields fit your workflow.

This Actor works with public profile information only. A result is not a guarantee that every public Snapchat account has every optional field available. For example, an avatar, display name, or follower count can be absent from a profile and is returned as `null` when unavailable.

### Why use this Actor?

- **Batch username input** — Check several public profiles in one run instead of collecting the same fields manually, making repeated research easier to organize.
- **Account-age context** — Receive both a human-readable `creation_date_text` and a calculated `account_age` so historical comparisons do not require separate spreadsheet formulas.
- **Date-friendly output** — Use `date_created` with its explicit `date_format` marker for a creation date without time-of-day noise.
- **Clear optional values** — The fields that may not be available—`display_name`, `avatar`, and `followers`—are represented as `null`, rather than replaced with invented values.
- **Structured profile rows** — Each successful profile produces the same documented set of fields, which makes it practical to review results as a table or pass them to a downstream process.
- **Adjustable parallel processing** — `maxConcurrency` lets you choose how many supplied profiles are processed at the same time, from 1 to 10.

### Who is this Actor for?

#### Creator and partnership researchers

Use the Actor to create a research list for publicly visible Snapchat profiles. The display name, follower value, account age, and latest available activity date give a compact starting point for comparing potential creators. Treat follower figures and profile details as source-reported values that can change over time; they should support human review, not replace it.

#### Social-profile operations teams

Teams maintaining a catalog of public social accounts can use the date fields to standardize their records. `date_created` provides a creation date in the documented day-first format, while `last_activity` offers a readable review value. The avatar URL and display name help distinguish accounts that have similar usernames.

#### Analysts building historical snapshots

Run a small list periodically and compare later datasets to observe public-profile changes. Preserve the run date alongside the results in your own reporting workflow, because the Actor returns the latest profile information available at the time of each run rather than a historical archive.

### Getting started

Start with one known public username. The leading `@` is optional.

```json
{
  "usernames": ["@exampleprofile"]
}
```

For a comparison list, provide all usernames you want to process and set the concurrency appropriate for the run.

```json
{
  "usernames": [
    "@profile_one",
    "profile_two",
    "@profile_three"
  ],
  "maxConcurrency": 2
}
```

For a first run in the Apify Console, add one username, keep the default limits, and inspect the resulting dataset. Confirm that the date formats and optional fields work for your use case before increasing the number of profiles.

### Input reference

| Parameter | Type | Default | Required | Description |
|---|---|---:|:---:|---|
| `usernames` | array of strings | — | Yes | Public Snapchat usernames to check. Values may include a leading `@`; each username must otherwise contain letters, numbers, periods, underscores, or hyphens. |
| `maxConcurrency` | integer | `3` | No | Number of supplied profiles processed at the same time. Choose a value from `1` to `10`; start conservatively for a new workflow. |

Only `usernames` is required. An empty list is not valid. Repeated usernames are deduplicated before processing.

### What data can you extract?

Each dataset row represents either a collected public Snapchat profile or a confirmed not-found profile. The example below uses invented values to show the exact output shape; it is not a claim about a real account.

```json
{
  "success": true,
  "status": "found",
  "username": "@exampleprofile",
  "display_name": "Example Profile",
  "avatar": "https://images.example.com/avatar.jpg",
  "followers": 120000,
  "creation_date_text": "April, 2021",
  "account_age": "5 Years 6 Months",
  "last_activity": "05-10-2026",
  "date_created": "01-04-2021",
  "date_format": "DD-MM-YYYY"
}
```

A confirmed not-found profile is retained in the dataset with `success: false` and `status: "not_found"`. Its profile-detail fields are `null`, so it can be distinguished from a request failure, which is reported in the run log rather than pushed as a dataset row.

| Field | Type | Description |
|---|---|---|
| `success` | boolean | `true` for a dataset row that was collected successfully. |
| `status` | string | `found` for a collected profile or `not_found` for a confirmed not-found response. |
| `username` | string | Public Snapchat username, always shown with a leading `@`. |
| `display_name` | string or null | Public display name when the profile provides one. |
| `avatar` | string or null | Public avatar image URL when available. |
| `followers` | integer or null | Available complete follower count, such as `950`, `12500`, or `3000000`. It is not a lifetime or guaranteed metric. |
| `creation_date_text` | string or null | Creation month and year, such as `April, 2021`, when the source provides `dateCreated`. |
| `account_age` | string or null | Elapsed age calculated from the creation date, such as `5 Years 6 Months`. This value changes as time passes. |
| `last_activity` | string or null | Latest available profile activity date in `DD-MM-YYYY` form. |
| `date_created` | string or null | Creation date in `DD-MM-YYYY` form, with no time component. |
| `date_format` | string | Always `DD-MM-YYYY`, the format used by `date_created` and `last_activity`. |

The `creation_date_text` and `account_age` values are useful for readable reports. For date calculations in a spreadsheet or database, parse `date_created` and `last_activity` according to `date_format`.

### Practical workflows

#### Build a public creator review list

Create a list of usernames from a campaign brief or an existing public catalog, then review `username`, `display_name`, `followers`, and `account_age` together. This creates a consistent first-pass table without inferring audience quality or engagement from follower counts alone. Use the results as an input to your team’s normal creator-review process.

#### Maintain a profile catalog

When a catalog stores public Snapchat accounts, run the Actor for the accounts being reviewed and compare the returned display name and avatar with your existing records. Parse `date_created` using `date_format` before chronological sorting. Optional fields can be `null`, so keep the existing value only when your own data-quality rules allow it.

#### Prepare a dated research snapshot

For a recurring research project, run the same small list at intervals and save each resulting dataset with the date of the run. Compare `followers`, `display_name`, and `last_activity` across snapshots. A missing value should be treated as unavailable for that run, not as evidence that the value is zero or unchanged.

### Tips for reliable results

Use exact public usernames whenever possible. Similar-looking names, extra spaces, and copied profile labels can lead to empty results because the Actor expects usernames rather than display names. Keep the leading `@` only when it helps your team read the list; it is optional for the input.

Begin with a small list, particularly when introducing the Actor to a new data flow. Verify that your destination can accept nullable fields and that date-only fields are treated as calendar dates rather than timestamps. If you use a spreadsheet, preserve `date_created` as text or explicitly parse it according to `date_format` to avoid locale-dependent conversions.

Choose `maxConcurrency` according to the size of the run and your operational preferences. A low value makes a short review run easy to observe, while a higher value is appropriate only after you have confirmed the desired fields. The maximum remains 10 concurrent profiles.

### Limitations and good-to-know details

This Actor is limited to public Snapchat profiles supplied by username. It does not promise that every username resolves to a profile or that every resolved profile exposes every optional field. A confirmed not-found response is retained as a `not_found` dataset row; other request failures are reported in the run log.

Public profile data can change after a run. Follower values may be absent; compact source values are converted to complete integer counts when they use a supported `K`, `M`, or `B` suffix. Display names and avatars can change, and the meaning of a profile’s latest available activity date is determined by the source platform. Do not treat an output row as proof of identity, ownership, endorsement, audience quality, or current activity beyond the returned public fields.

The Actor provides only the documented profile fields. It does not provide private account information, messages, contact details, audience demographics, engagement analytics, media archives, or a guarantee of exhaustive coverage. Plan for incomplete values in any automated workflow.

### Troubleshooting

| Symptom | Likely cause | What to inspect or change |
|---|---|---|
| A `not_found` dataset row | Snapchat confirmed that the public profile was not found. | Check the username spelling and whether the profile is publicly available. |
| Fewer rows than usernames | A transient request or proxy failure prevented collection after retries. | Review the run log, then retry the affected usernames. |
| A display name, avatar, or follower value is `null` | The profile did not expose that optional value for the run. | Keep the null value in downstream data or apply your own missing-data policy; do not replace it with a guess. |
| Missing expected rows | Some supplied values may be duplicates. | Compare the input list with the resulting `username` values and use a cleaned list for diagnosis. |
| Date fields do not sort as expected | A destination may treat day-first date strings as locale-formatted text. | Parse `date_created` using `date_format` before sorting. |
| The run cannot use selected platform options | The option may not be available to the account or may conflict with the run configuration. | Review the selected Apify platform settings and account access before retrying. |

### Responsible use

Use this Actor only for legitimate purposes and only with public information that you are entitled to collect and use. Public availability does not remove privacy, intellectual-property, contract, marketing, or jurisdictional obligations. Do not use the results to impersonate people, infer sensitive traits, harass individuals, or make high-impact decisions about a person without appropriate safeguards and independent review.

If results are used for outreach, research, or analytics, make sure your downstream activity complies with applicable law, platform terms, and your organization’s policies. Keep the scope proportionate to your purpose, minimize retention of personal information, and give special care to data about minors or vulnerable people.

### Frequently asked questions

#### Do I need to include `@` before each username?

No. The input accepts usernames with or without `@`. Output usernames include `@` so records have a consistent display format.

#### What does `account_age` mean?

It is an elapsed value calculated from the available creation date. It is intended for readable reporting and changes over time; use `date_created` when you need to perform your own date calculation.

#### Why is a follower value missing?

`followers` is optional. A `null` value means it was not available for that public profile during the run, not that the account has no followers.

#### Are the detailed dates timestamps?

No. `date_created` contains only the calendar date in `DD-MM-YYYY` form, and `date_format` identifies that format. No hours, minutes, seconds, or time zone are included.

#### Can I process more than one account?

Yes. Supply every username in the `usernames` array; the Actor processes the complete deduplicated list.

#### Does the Actor return errors as dataset rows?

No. The dataset contains successful profile rows. Review the run details and your input list when a requested account does not appear in the results.

Start with a small, known-public username list and inspect the resulting fields before increasing scope. The structured output is most useful when combined with clear downstream rules for missing values, dated snapshots, and responsible handling of public profile information.

# Actor input Schema

## `usernames` (type: `array`):

Public Snapchat usernames. An optional leading @ is accepted.

## `maxConcurrency` (type: `integer`):

Number of profiles to process at the same time.

## Actor input object example

```json
{
  "usernames": [
    "@exampleprofile"
  ],
  "maxConcurrency": 3
}
```

# Actor output Schema

## `results` (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 = {
    "usernames": [
        "@exampleprofile"
    ]
};

// Run the Actor and wait for it to finish
const run = await client.actor("karamelo/snapchat-account-age-checker-and-last-activity").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 = { "usernames": ["@exampleprofile"] }

# Run the Actor and wait for it to finish
run = client.actor("karamelo/snapchat-account-age-checker-and-last-activity").call(run_input=run_input)

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

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

```

## CLI example

```bash
echo '{
  "usernames": [
    "@exampleprofile"
  ]
}' |
apify call karamelo/snapchat-account-age-checker-and-last-activity --silent --output-dataset

```

## MCP server setup

```json
{
    "mcpServers": {
        "apify": {
            "type": "http",
            "url": "https://mcp.apify.com/?tools=fetch-actor-details,karamelo/snapchat-account-age-checker-and-last-activity"
        }
    }
}
```

The hosted server signs you in with OAuth on first connect, so no API token belongs in this config. Clients without OAuth support can send an `Authorization: Bearer <APIFY_API_TOKEN>` header instead, using a token from API & Integrations in Apify Console (https://console.apify.com/settings/integrations).

## OpenAPI specification

Download the OpenAPI definition: https://api.apify.com/v2/actors/pDsRurWrOyLHMrdbt/builds/d7HcQFOXhbMJP27s9/openapi.json