Beehiiv Newsletter & Post Scraper

Turn public Beehiiv newsletters into structured data for research, analysis, monitoring, and downstream workflows. Supply one or more publication or post URLs and receive clean newsletter profiles and public post records in the default Apify dataset.

Use the Actor to build newsletter archives, compare publishing activity, research topics and authors, or collect public article text and metadata for further analysis.

What you can collect

Depending on the selected mode, each run can return:

• Newsletter profiles — publication name, description, canonical URL, and image.
• Public posts — title, description, author, publication date, image, canonical URL, publication details, and public article content.
• Full public content when needed — extracted article text and HTML can be included or omitted to keep results smaller.

You can start from publication homepages, Beehiiv custom domains, or individual public post URLs.

Private, subscriber-only, email-only, and paywalled content is not bypassed.

Common use cases

• Build a structured archive of a public Beehiiv newsletter.
• Research newsletter topics, titles, authors, and publishing dates.
• Compare public content across multiple Beehiiv publications.
• Collect post text for text analysis or other downstream processing.
• Extract publication profiles without collecting individual posts.
• Filter an archive to posts published after a date or matching selected keywords.

How to use the Actor

Add one or more public Beehiiv publication or post URLs in startUrls, then choose what to collect:

• posts — collect public post records. This is the default.
• profiles — collect newsletter profile records only.
• both — collect profiles and posts.

Example input:

{
  "startUrls": [{"url": "https://product.beehiiv.com"}],
  "mode": "both",
  "maxItems": 25,
  "includeContent": true,
  "publishedAfter": "2025-01-01",
  "keywords": ["growth", "newsletter"]
}

Main inputs

Input	What it does
startUrls	Public Beehiiv publication homepages, custom-domain publication URLs, or individual post URLs. Required.
mode	Selects posts, profiles, or both.
maxItems	Sets the maximum number of post records to collect, from 1 to 10,000. Profile records are additional in both mode.
includeContent	Includes or omits public article text and HTML.
publishedAfter	Keeps posts published on or after the supplied ISO 8601 date or date-time.
keywords	Keeps posts matching at least one keyword in the title, description, or extracted content.

Concurrency, retry, and timeout controls are also available for larger or more specialised runs.

Results

Results are written to the default Apify dataset. Each item is either a profile or post record and includes recordType so mixed runs are easy to separate.

Example post result:

{
  "recordType": "post",
  "url": "https://product.beehiiv.com/p/example",
  "publicationUrl": "https://product.beehiiv.com/",
  "publicationName": "beehiiv product updates",
  "title": "Example update",
  "description": "A concise preview",
  "author": "Example Author",
  "publishedAt": "2025-01-15T12:00:00Z",
  "imageUrl": "https://example.com/image.png",
  "contentText": "Public article text…",
  "contentHtml": "<article>…</article>"
}

Run metadata is available separately in the key-value store:

• SUMMARY — record, request, and failure counts.
• FAILURES — input-level errors when some supplied inputs could not be processed.

Control your results

Use maxItems to cap the number of posts returned. Set includeContent to false when you only need titles, metadata, and URLs rather than full article bodies.

Use publishedAfter to focus on newer posts and keywords to keep records matching topics relevant to your research.

Pricing

This Actor uses pay-per-result pricing at USD $2.50 per 1,000 dataset results ($0.0025 per result).

Each profile or post written to the default dataset counts as one billable result. SUMMARY and FAILURES are stored separately and are not billed as dataset results.

Limitations

• Only publicly available content from supplied publications or post URLs is returned.
• Publishers can remove pages, change metadata, restrict publications, or alter their public sites.
• Custom domains must expose a Beehiiv-compatible /sitemap.xml for archive collection.
• The Actor does not discover unknown newsletters or browse Beehiiv's directory for you.

Support

For a reproducible support report, include the sanitized Actor input, run ID, affected public URL, and expected versus actual behaviour. Do not include cookies, tokens, subscriber data, or private content.