WordPress Public Content Change API

Monitor published WordPress post or page metadata and excerpts through the public REST API, with stable hashes and explicit bounded pagination.

Quick start

{
  "urls": [
    "https://wordpress.org/news/"
  ],
  "maxItems": 5,
  "contentType": "posts"
}

Download the default dataset as JSON, CSV or Excel. Read OUTPUT before relying on completeness; source availability can change. Use sources you are authorized to access.

Documented behavior and limits

Reads only public published posts or pages, with a selected-field REST request. Returns title, excerpt (plain text, at most 1200 characters), URL, slug, published/modified GMT strings, identity and hash. Does not query users, comments, drafts, private posts or admin endpoints. Password-protected records are skipped. At most three installation roots, five pages of ten records and 50 emitted records per root. A short page or declared final page ends the query; duplicates, source errors, skipped protected records and record/page caps make completeness false. No missing-record deletion inference. Metadata/excerpt changes are detected; edits beyond the returned fields or truncated excerpt may be missed. GMT timestamps are source-reported fields, not independent verification. An empty public collection is a valid zero-result observation.

Changes and snapshots

Each result includes itemKey, contentHash and observedAt. Pass SNAPSHOT.previousHashes in the next input. NO_BASELINE means no prior map; FIRST_SEEN means absent from a supplied map; UNCHANGED/CHANGED compare hashes. FIRST_SEEN does not prove newly created content. Snapshot contains only emitted rows. Missing rows are not deletions. No hidden persistence or scheduled tasks. For header observations, redirect trace is excluded from the hash; it remains in output. Other observations hash their normalized fields, excluding pagination source URL and time.

Pricing

$0.001 per emitted content observation ($1 per 1,000), plus $0.005 Actor-start at the default 256 MB. Higher memory can multiply startup events under Apify rules. Event-only pricing includes platform usage; no paid upstream API, proxy or browser. Failed sources incur no result event, but the start event can apply. An intentional missing-policy observation is billable for the robots product. Check Store pricing before running. Budget truncation sets PARTIAL_BUDGET and complete=false.

Network and data

Public HTTP(S), ports 80/443 only; credentials and private IPs rejected. DNS addresses are validated and pinned while TLS hostname verification stays enabled. Up to five redirects, 2 MiB decoded responses and approximately 95 seconds network budget. Site/content/spec fetches respect robots.txt; missing 404/410 policy allows access, unavailable/denied policy is an error. The robots product reads the policy file itself and never requests the evaluated page. No login, cookies, proxy, access-block workaround, external reference fetching or active security tests. All failed sources are reported; successful sources can continue. A run with no rows and source errors fails; valid empty collections/specs can succeed. Sources, redirects and their robots files are the only network targets. Inputs and output stay in your Apify run storage under platform retention; no separate customer analytics endpoint. Do not provide secrets.

Integration and support

POST https://api.apify.com/v2/actors/soilair~wordpress-public-content-change-api/runs with your Apify authorization header and input JSON. Poll the returned run and retrieve its defaultDatasetId and defaultKeyValueStoreId for OUTPUT/SNAPSHOT. Configure integrations/schedules in Console if needed; the Actor creates neither. Developed with AI assistance, fixtures and public-source/cloud checks. Examples do not establish arbitrary-source compatibility. Report a run ID and expected behavior through the issue tab without credentials.

Source specification: https://developer.wordpress.org/rest-api/reference/posts/