WordPress Plugin Version & Requirement Evidence API
Pricing
from $1.00 / 1,000 metadata observations
WordPress Plugin Version & Requirement Evidence API
Watch exact WordPress.org plugin slugs for version, declared WordPress/PHP requirements and tested-up-to text. Stable snapshots without reviews, author profiles, downloads or installs.
Pricing
from $1.00 / 1,000 metadata observations
Rating
0.0
(0)
Developer
Salih Can Kurnaz
Maintained by CommunityActor stats
0
Bookmarked
2
Total users
1
Monthly active users
3 days ago
Last modified
Categories
Share
For a small WordPress maintenance watchlist, request public plugin_information metadata from the official WordPress.org API1.2. Require the exact returned slug and a nonempty version. Select version, minimum WordPress/PHP strings, tested-up-to string, direct required plugin slugs and the source last_updated text. last_updated is kept in its original source notation, including GMT when supplied; no UTC conversion is inferred. Version constraints and tested-up-to are not executed or solved and do not guarantee compatibility, safety, support or installability. No ZIP files, PHP execution, website logins, upgrades, security verdicts, reviews, ratings, installs, author/contact profiles, screenshots, icons, descriptions, upgrade notices or HTML fields are emitted. Heavy optional fields are disabled in the request; some source defaults can still be returned but are discarded. Missing values remain null. A missing/error response does not establish that a plugin was deleted, closed or safe. Intended for snapshot comparison of known slugs, not directory harvesting.
Input example
{"slugs": ["akismet","contact-form-7"],"maxResults": 2}
Outputs and change comparison
One saved observation is one dataset row with itemKey, sourceUrl, contentHash and observedAt. The SHA256 covers only selected semantic fields; retrieval times, API request URLs, download/popularity counters and people are excluded. Copy SNAPSHOT.previousHashes into the next input to compare the same exact watchlist. Statuses are NO_BASELINE, FIRST_SEEN, UNCHANGED or CHANGED. Unchanged observations are still billable. There is no hidden persistent baseline and no missing-row/deletion inference. OUTPUT records actual requestCount, rowsEmitted, source summaries, errors, status and complete. SNAPSHOT.complete is false after any error or when any requested observation could not be delivered. Reaching the selected result cap is PARTIAL_RESULT_CAP; a monetary budget stop is PARTIAL_BUDGET. Provider restrictions produce PARTIAL_PROVIDER_LIMIT. A saved observation means successful metadata extraction only, not an independent validation or entitlement decision.
Pricing and bounded work
$0.005 startup plus $0.001 per saved observation, pay per event. Startup quantity follows Apify memory rules with minimum one. Minimum permitted run budget: $0.0055. Default 256 MB, timeout 120 seconds, no restart. Five identifiers and at most five rows; a 55-second fetch deadline and two-MiB decoded-body cap apply. API requests are made only after checking the affordable result capacity. Zero affordable observations causes zero source requests, including no provider request. Before each later request and dataset write the budget is checked again. Responses that do not produce a saved row are not charged as observations; startup can still apply. No browser, paid proxy, paid external API or credentials. No network retries, bypasses, open-ended search or bulk pagination. Shared-IP provider limits still apply across runs: avoid parallel requests that exceed provider policy and use supported bulk data channels for large extraction.
Failure and access behavior
Only constructed official HTTPS API endpoints are contacted. Only fixed provider endpoints constructed from validated identifiers are contacted. Private addresses and credential-bearing/cross-provider redirects are rejected. HTTP403/429 or Retry-After stops further provider work; successful current responses can be retained. Unknown/missing identifiers are errors, never guessed missing/safe states. All-source failure exits nonzero after preserving OUTPUT; partial delivery preserves successful rows and explicit errors. Source versions and raw declarations can change, and the Actor does not independently verify artifact bytes, publisher identity, signatures or legal rights. Public upstream APIs/data may be free; the fee covers the bounded selection, validation, comparison/output workflow and Apify execution. There is no affiliation, exclusive data access, guaranteed availability, completeness or revenue claim.