🔗 LinkedIn Post Creation Date Extractor

Instantly reveal the exact creation date and time of any public LinkedIn post — no login, no scraping headaches, no anti-bot rabbit holes. Just paste a URL, run, and get a precise UTC timestamp down to the millisecond.

⭐ Why Choose Us?

• ⚡ Lightning fast — decoding is offline math; results in milliseconds per URL.
• 🔁 Bulk friendly — paste hundreds of URLs at once.
• 🛡️ Smart proxy fallback — starts direct, escalates to datacenter, then residential only when LinkedIn pushes back.
• 🪶 Lightweight — no headless browser, no Playwright overhead.
• 🧠 Robust — handles /posts/..., feed updates, and raw urn:li:activity:... formats.
• 💾 Live saving — every result is pushed to the dataset as soon as it's ready.

✨ Key Features

• 🔗 Accepts LinkedIn post URLs and activity URNs
• 📅 Returns precise UTC creation_date, ISO date, and millisecond timestamp
• 🌐 Optional URL reachability check
• 🛡️ Direct → datacenter → residential proxy escalation (sticky after fallback)
• 🔁 Configurable retries with exponential backoff
• 📊 Rich dataset view with column labels and emoji headers
• 🪵 Engaging real-time logs that show progress per URL

📥 Input

{
  "urls": [
    { "url": "https://www.linkedin.com/posts/fredericjousset_chaque-jour-avec-la-m%C3%AAme-r%C3%A9gularit%C3%A9-implacable-activity-7218859278495813634-nG42" }
  ],
  "validateUrl": true,
  "proxyConfiguration": { "useApifyProxy": false }
}

Field	Type	Description
urls	array	LinkedIn post URLs or activity URNs (bulk supported)
validateUrl	boolean	Whether to also confirm the URL is reachable
proxyConfiguration	object	Apify proxy settings; defaults to no proxy

📤 Output

{
  "url": "https://www.linkedin.com/posts/fredericjousset_chaque-jour-avec-la-m%C3%AAme-r%C3%A9gularit%C3%A9-implacable-activity-7218859278495813634-nG42",
  "activity_id": "7218859278495813634",
  "creation_date": "2024-07-16 06:09:31.913000",
  "creation_date_iso": "2024-07-16T06:09:31.913000+00:00",
  "creation_timestamp_ms": 1721110171913,
  "url_reachable": true,
  "http_status": 200,
  "proxy_used": "direct",
  "success": true,
  "error": null
}

Field	Description
url	Original input URL
activity_id	LinkedIn 19-digit activity ID
creation_date	Human-readable UTC date YYYY-MM-DD HH:MM:SS.ffffff
creation_date_iso	ISO 8601 datetime
creation_timestamp_ms	Unix timestamp in milliseconds
url_reachable	true/false/null (when validation disabled)
http_status	HTTP status of the validation request
proxy_used	direct, datacenter, or residential
success	Did the timestamp decode succeed
error	Error string if any

🚀 How to Use (Apify Console)

1. Log in at console.apify.com → Actors.
2. Open LinkedIn Post Creation Date Extractor.
3. Paste your LinkedIn URLs in the URLs field.
4. (Optional) Toggle Validate URL off for offline-only decoding.
5. Click Start.
6. Watch the real-time logs.
7. Open the Output tab when the run completes.
8. Export results to JSON / CSV / XLSX.

🤖 Use via API

curl -X POST "https://api.apify.com/v2/acts/<ACTOR_ID>/run-sync-get-dataset-items?token=$APIFY_TOKEN" \
     -H "Content-Type: application/json" \
     -d '{
       "urls": [
         {"url": "https://www.linkedin.com/posts/fredericjousset_activity-7218859278495813634-nG42"}
       ],
       "validateUrl": false
     }'

🛡️ Proxy Strategy

The actor begins with no proxy to keep latency low. If LinkedIn returns a blocking status (403, 407, 429, 451, 503) or a network error occurs, it escalates:

1. 🟢 Direct — first attempt
2. 🟡 Datacenter (Apify proxy) — fast fallback
3. 🔴 Residential — last resort, retries up to 3 times with exponential backoff

Once the actor falls back, it stays on the higher tier (sticky) for the rest of the run — no flapping.

💡 Best Use Cases

• 📰 Newsroom verification — confirm post timing for citations
• 📊 Marketing analytics — line up campaign posts with engagement
• 🔍 OSINT and research — establish when a public post first appeared
• 🗂️ Archival — keep a historical index of posts with exact timestamps

💸 Pricing

This actor uses the pay-per-event model. You pay only for what you decode.

Event	When charged
apify-actor-start	Once when a run begins (synthetic, configured in Console)
result-item	Each successfully resolved post (a creation_date was decoded)

Failed lookups (e.g. malformed URLs) are not billed.

❓ Frequently Asked Questions

Q: Do I need to log in to LinkedIn? A: No. The creation date is encoded inside the activity ID, which is public.

Q: Does it work with private posts? A: As long as the URL contains a numeric activity ID, yes — the timestamp is decoded mathematically, no fetch needed.

Q: Will I get rate-limited? A: With validation off, no requests are sent at all. With validation on, the actor escalates through proxy tiers automatically.

Q: What if a URL has no activity ID? A: It's pushed to the dataset with success: false and error: "no activity id found" so you can audit it.

📬 Support and Feedback

Open an issue or contact the maintainer via the Apify Store listing. Feedback welcome 💬.

⚖️ Legal

• Only public, anonymously-accessible URLs are processed.
• The end user is responsible for compliance with LinkedIn's Terms of Service, GDPR, CCPA, and other applicable laws.
• The actor never logs in, never bypasses auth walls, never accesses private content.