WordPress Posts — Public Data to JSON

Export public posts from WordPress sites that expose the standard WP REST API. Use this lightweight Apify Actor when you need reliable JSON-shaped data from a known public source, without setting up an external scraper server.

Designed for: Content analysts, website auditors and marketing automation developers.

Try a ready-made example: Open this Actor's public Example Task to start with a three-result input, without writing JSON. You can adjust the source and limits before running. Review the Pricing tab first; usage is not necessarily free.

Quick preview: what you get

Export public WordPress posts and excerpts from a site's REST API. Requires an accessible wp-json/wp/v2/posts endpoint.

Small example input (3 results):

{
  "sources": [
    "https://wordpress.org/news/"
  ],
  "maxTotalItems": 3,
  "maxItemsPerSource": 3
}

Illustrative output, not a live result:

{
  "status": "ok",
  "id": 123,
  "title": "Illustrative post",
  "url": "https://example.org/article",
  "excerpt": "Example text"
}

Run with the example in the Input tab, then inspect Output. If the public source is unavailable or blocks access, you will receive an error rather than fabricated data.

What can you do with it?

Blog content synchronization and recent-post monitoring. Configure a recurring Apify schedule, integrate its dataset into existing automations, or fetch results via the Apify API. The Actor produces one structured dataset item per successful record, enabling easy import into spreadsheets or downstream services.

It uses public HTTPS requests and a lightweight Python parser — no browser, residential proxy, login, or external paid AI provider. Data is returned as the source provides it; the Actor does not fabricate missing fields.

Quick start — no coding required

1. Open the Input tab and add the public source URL or identifier.
2. Set Max results to 3 for a small first test.
3. Click Start and inspect the Output tab.
4. Export the resulting dataset as JSON or CSV, or use the API and scheduling options in your Apify account.

Output fields

id, title, url, excerpt. Each row additionally contains status and input, so downstream automation can trace where a record came from.

Limits and source coverage

Works only if wp-json/wp/v2/posts is publicly accessible. No private posts, login, media downloading or deeper crawling. Supported requests use HTTPS only. Each run accepts up to 15 input sources, 40 upstream HTTP requests, 2 MB per upstream response and 250 successful output records. One source's error is reported as an error row rather than silently ignored.

This is a public-data extractor, not an account bypass, private-data service or full-site crawler. If a provider blocks, changes or rate-limits its public endpoint, its data may not be available. Follow the source's terms and applicable data-use requirements.

How much does it cost?

The live Pricing tab shows the current charges for this Actor. Where Pay Per Event is enabled, the result-item event is for a successful record. Do not assume that attempted, blocked or missing results become paid records. Always consult the active Pricing tab before using this Actor at scale. For a safe pilot, start with 3 results and set a maximum run charge where available. If platform usage is charged separately, the Pricing tab will disclose it.

We do not claim a guaranteed 50% discount, unlimited results, 100% uptime, or that every source is accessible. If this Actor is not yet publicly listed, its price and features remain under review.

Related tools on Apify

RSS / Atom Feed Items — parse public feeds from websites that do not expose a WordPress REST endpoint.

These are separate Actors with separate pricing and source limitations. Check each Actor's Pricing and Input tabs.

Troubleshooting and support

Empty data or a source error? Check the public /wp-json/wp/v2/posts endpoint. Some sites restrict WordPress REST access. Try the smallest possible input and verify the public endpoint independently.

Can I schedule it? Yes. Apify provides scheduling, datasets, monitoring and integration options for your Actor runs.

Will I get results from private accounts? No. There is no account login or credential input, and inaccessible sources cannot be bypassed.

Need help or found a bug? Use the Issues tab of this Actor with a public reproducible example. Do not post passwords, API tokens or private data. Issues help us improve parsing reliability and document provider-specific limitations.

---

Micro Tool Factory — purpose-built public-data utilities. This description reflects implemented capabilities, not invented testimonials or guaranteed customer outcomes.