Discover/WordPress API
live

WordPress APIwordpress.org

Access WordPress.org usage statistics: WordPress core versions, PHP versions, MySQL/MariaDB versions, and locale distributions across millions of sites.

Endpoint health
verified 7d ago
get_mysql_stats
get_locale_stats
get_wordpress_stats
get_php_stats
get_all_stats
5/5 passing latest checkself-healing
Endpoints
5
Updated
22d ago

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.

Try it

No input parameters required.

api.parse.bot/scraper/1310e85e-fdf6-428d-958c-002d157ffe03/<endpoint>
Ready to send
Fill in the parameters and hit sign in to send to see live response data here.
Call it over HTTPgrab a free API key at signup
curl -X GET 'https://api.parse.bot/scraper/1310e85e-fdf6-428d-958c-002d157ffe03/get_wordpress_stats' \
  -H 'X-API-Key: $PARSE_API_KEY'
Python SDK · recommended

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")
All endpoints · 5 totalmissing one? ·

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.

Input

No input parameters required.

Response
{
  "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.

Reliability & maintenanceVerified

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.

Last verified
7d ago
Latest check
5/5 endpoints passing
Maintenance
Monitored & self-healing
Will this API break when the source site changes?+
It's built not to. Every endpoint is health-checked on a schedule with automated test probes. When the source site changes and a check fails, the API is automatically queued for repair and re-verified — that's the self-healing layer. Each API page shows when its endpoints were last verified. And because marketplace APIs are shared, any fix reaches everyone using it.
Is this an official API from the source site?+
No — Parse APIs are independent, managed REST wrappers over publicly available data. That is the point: where a site has no official API (or only a limited one), Parse gives you a maintained, monitored endpoint for that data and keeps it working as the site changes — so you get a stable contract over a source that never promised one.
Can I fix or extend this API myself if I need a new endpoint or field?+
Yes — and you don't have to wait on us. This API was generated by the Parse agent, which stays attached. Describe the change in plain English ("add an endpoint that returns reviews", "fix the price field") in the revise box on the API page or via the revise_api MCP tool, and the agent rebuilds it against the live site in minutes. Contributing the change back to the public API is free.
What happens if I call an endpoint that has an issue?+
Errors are machine-readable: a bad call returns a clean status with the list of available endpoints and a repair hint, so an agent (or you) can recover or trigger a fix instead of failing silently. Confirmed failures feed the automatic repair queue.
Common use cases
  • 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_stats and get_php_stats data to profile the infrastructure stack of the average WordPress deployment
Pricing & limitsSee full pricing →
TierPriceCredits/monthRate limit
Free$0/mo1005 req/min
Hobby$30/mo1,00020 req/min
Developer$100/mo5,000100 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.

Frequently asked questions
Does WordPress.org have an official public statistics API?+
Yes. WordPress.org exposes a public stats endpoint at https://api.wordpress.org/stats/wordpress/1.0/ and related paths for PHP, MySQL, and locale data. This API wraps those public endpoints and normalizes their responses into a consistent JSON structure.
What does `get_mysql_stats` return, and does it separate MySQL from MariaDB?+
It returns a 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?+
Not currently. All five endpoints return global aggregate distributions with no filtering by region, plugin, or theme category. You can fork this API on Parse and revise it to add filtered or segment-specific endpoints if the upstream source exposes that data.
Does the API provide historical time-series data for any of the stats?+
Not currently. Each endpoint returns a current snapshot of the distribution. 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?+
The 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.
Page content last updated . Spec covers 5 endpoints from wordpress.org.
Related APIs in Developer ToolsSee all →
pageviews.wmcloud.org API
Access Wikipedia pageview analytics across articles, languages, and time periods. Retrieve per-article view counts, top-viewed pages, cross-language traffic breakdowns, site-wide aggregates, category-level mass analysis, redirect traffic attribution, user contribution metrics, and Wikimedia Commons media request counts.
worlddata.info API
Explore global statistics and compare countries across population, economy, demographics, quality of life, education, and health metrics. Search worldwide data on everything from life expectancy and languages to religions and regional breakdowns to gain comprehensive insights into how nations rank against each other.
worldometers.info API
Track current world population statistics, compare country rankings, and explore historical population trends and future projections. Monitor demographic changes across nations and understand global population dynamics in real-time.
viewstats.com API
viewstats.com API
argenstats.com API
Access Argentina's key economic indicators including the EMAE activity index, inflation (IPC), dollar exchange rates (BLUE, CCL, MEP, OFICIAL, and more), country risk, employment, and poverty levels. Retrieve current values, historical series, and forecasting event listings from ArgenStats.
woocommerce.com API
Browse and search thousands of WooCommerce extensions, themes, and business services from the official marketplace while accessing detailed product information, user reviews, and ratings. Integrate marketplace data, blog content, and documentation directly into your applications to help users discover and learn about WooCommerce solutions.
openclipart.org API
Search and discover clipart from OpenClipart, explore collections by tag, and retrieve detailed metadata including artist profiles, engagement metrics, and download URLs. Also exposes site-wide statistics such as total clipart count, artist count, and recent upload activity.
similarweb.com API
Analyze any website's performance by retrieving detailed traffic statistics, visitor demographics, geographic distribution, competitor benchmarks, and search source data. Monitor engagement metrics and rankings to understand how websites compare in your industry and discover new competitive opportunities.