WordPress APIwordpress.org ↗
Access WordPress.org usage statistics: WordPress core versions, PHP versions, MySQL/MariaDB versions, and locale distributions across millions of sites.
What is the WordPress API?
This API exposes 5 endpoints covering WordPress.org public usage statistics, including the distribution of WordPress core versions, PHP runtimes, database versions, and locales across the global WordPress install base. The get_all_stats endpoint aggregates all four data categories in a single call, while individual endpoints like get_php_stats and get_mysql_stats return focused distribution data mapping version strings to percentage values.
No input parameters required.
curl -X GET 'https://api.parse.bot/scraper/1310e85e-fdf6-428d-958c-002d157ffe03/get_wordpress_stats' \ -H 'X-API-Key: $PARSE_API_KEY'
Typed, relational, agent-ready
A generated client with real types, enums, and the links between objects — the structure a flat JSON response can't carry. Autocompletes in your editor and reads cleanly to coding agents.
- Fully typed · autocompletes
- Objects link to objects
- Typed errors & pagination
Typed Python client. Set up the SDK in your uv project, then pull this API’s typed client:
uv add parse-sdk uv run parse init uv run parse add --marketplace wordpress-org-api
uv run parse add --marketplace pulls a pinned snapshot of this canonical API — it won’t change underneath you. To customize it, subscribe and swap to your own copy.
"""Walkthrough: WordPress.org Statistics SDK — version adoption and ecosystem health."""
from parse_apis.wordpress.org_statistics_api import WordPressStats, UpstreamError
client = WordPressStats()
# Fetch WordPress version distribution — single call, typed result.
wp = client.distributions.wordpress()
print(f"WordPress stats source: {wp.source}")
for version, pct in sorted(wp.data.items(), key=lambda x: x[1], reverse=True)[:5]:
print(f" WP {version}: {pct}%")
# Fetch PHP version distribution to assess security posture.
php = client.distributions.php()
print(f"\nPHP stats: {php.description}")
for version, pct in sorted(php.data.items(), key=lambda x: x[1], reverse=True)[:3]:
print(f" PHP {version}: {pct}%")
# Database distribution — MySQL vs MariaDB split.
db = client.distributions.mysql()
print(f"\nDatabase stats from: {db.source}")
for version, pct in sorted(db.data.items(), key=lambda x: x[1], reverse=True)[:3]:
print(f" {version}: {pct}%")
# Typed error handling on a real call.
try:
locales = client.distributions.locales()
print(f"\nLocales tracked: {len(locales.data)} languages")
for lang, pct in sorted(locales.data.items(), key=lambda x: x[1], reverse=True)[:3]:
print(f" {lang}: {pct}%")
except UpstreamError as exc:
print(f"Upstream error: {exc}")
# Aggregated call — all four distributions in one round-trip.
all_stats = client.distributions.all()
print(f"\nAggregated stats generated at: {all_stats.generated_at}")
print(f" WP versions tracked: {len(all_stats.data.wordpress_versions)}")
print(f" PHP versions tracked: {len(all_stats.data.php_versions)}")
print(f" DB versions tracked: {len(all_stats.data.mysql_versions)}")
print(f" Locales tracked: {len(all_stats.data.locales)}")
print("\nexercised: distributions.wordpress / .php / .mysql / .locales / .all")
Get WordPress version distribution statistics showing the percentage of WordPress sites using each version. Returns an object mapping version strings to their adoption percentage. No input parameters required.
No input parameters required.
{
"type": "object",
"fields": {
"data": "Object mapping WordPress version numbers (e.g. '7.0', '6.9', '6.8') to their adoption percentage as a float",
"source": "API endpoint URL used to fetch the data",
"description": "Description of the data returned"
},
"sample": {
"data": {
"data": {
"6.8": 8.05,
"6.9": 20.277,
"7.0": 51.624
},
"source": "https://api.wordpress.org/stats/wordpress/1.0/",
"description": "WordPress version distribution among all WordPress sites"
},
"status": "success"
}
}About the WordPress API
What the API Returns
Each endpoint returns a data object mapping version or locale strings to percentage values — for example, {'8.2': 14.3, '7.4': 22.1} from get_php_stats, or {'English (US)': 63.1, 'German': 4.2} from get_locale_stats. Every response also includes a source field identifying the upstream URL and a description field summarizing the dataset.
Endpoints Overview
get_wordpress_stats returns the share of active WordPress installs per core version (e.g. 6.9, 6.8). get_php_stats covers PHP version adoption. get_mysql_stats breaks down database engine versions, distinguishing between MySQL and MariaDB variants such as MySQL 8.0 and MariaDB 10.11. get_locale_stats shows language distribution by locale name. None of these endpoints require input parameters.
Aggregated Call
get_all_stats combines all four datasets under the keys wordpress_versions, php_versions, mysql_versions, and locales in a single response. It also includes a generated_at field in ISO 8601 UTC format, useful for tracking when the snapshot was taken. This is the most efficient option when you need a full picture of the WordPress ecosystem in one request.
Data Scope and Freshness
All statistics reflect the distribution across the WordPress.org install base and are expressed as percentages. The data mirrors what WordPress.org publishes publicly through its statistics service. Coverage is global with no regional filtering available at the endpoint level.
The WordPress API is a managed, monitored endpoint for wordpress.org — not a raw scraper you maintain. Every endpoint is automatically health-checked on a schedule, and when wordpress.org changes and a check fails, the API is automatically queued for repair and re-verified. It is built to keep working as the site underneath it changes.
This isn't an official wordpress.org API — it's an independent, maintained REST wrapper over public data. Where the source has no official API (or only a limited one), Parse gives you a stable contract over a source that never promised one, and keeps it current. Need a new endpoint or field? You can revise it yourself in plain English and the agent rebuilds it against the live site in minutes — contributing the change back to the shared API is free.
Will this API break when the source site changes?+
Is this an official API from the source site?+
Can I fix or extend this API myself if I need a new endpoint or field?+
What happens if I call an endpoint that has an issue?+
- Track PHP version adoption trends to decide which PHP versions a WordPress plugin should officially support
- Monitor WordPress core version distribution to assess how quickly sites update after a new release
- Identify the share of sites still running end-of-life MySQL or MariaDB versions for security research
- Analyze locale distribution data to prioritize translation efforts for a WordPress theme or plugin
- Feed WordPress and PHP version stats into a CI matrix to determine which version combinations to test against
- Report on WordPress ecosystem fragmentation by charting core version spread over time using
get_wordpress_stats - Combine
get_mysql_statsandget_php_statsdata to profile the infrastructure stack of the average WordPress deployment
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 100 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does WordPress.org have an official public statistics API?+
What does `get_mysql_stats` return, and does it separate MySQL from MariaDB?+
data object where each key is a database version string such as MySQL 8.0 or MariaDB 10.11, and the value is the percentage of WordPress sites running that version. MySQL and MariaDB are listed as distinct entries, so you can compare their shares directly.Can I filter statistics by country or WordPress.org plugin/theme category?+
Does the API provide historical time-series data for any of the stats?+
get_all_stats includes a generated_at timestamp for the retrieval moment, but there is no built-in history or trend data. You can fork the API on Parse and revise it to add a scheduled polling endpoint that stores snapshots over time.What is the `source` field in each response?+
source field contains the URL of the upstream WordPress.org statistics endpoint that corresponds to that dataset. It lets you verify or cross-reference the data origin for each call.