oanor
Sign up free
Marketplace Pricing Features Sign in

API · /wordpress-api

WordPress Directory API

healthy 3,638 Subscribers

The official WordPress.org plugin and theme directory as an API — the registry behind the ~40% of the web that runs on WordPress. Look up any plugin or theme by its slug for its name, version, author, user rating and rating count, active-install count and total downloads, the WordPress and PHP versions it requires, last-updated date, homepage, support URL and direct download link; and search the directory by keyword (plugins or themes), with results ranked by active installs. Covers the 60,000+ free plugins and 13,000+ themes on WordPress.org, from WooCommerce, Yoast SEO and Elementor to Contact Form 7 and Jetpack. Live from the official api.wordpress.org. Ideal for WordPress dashboards and site managers, plugin/theme catalogs, compatibility and update tooling, and the WordPress developer ecosystem. Open data from WordPress.org.

#wordpress #plugins #themes #cms #developer-tools #web
api.oanor.com/wordpress-api
Get an API key Try in playground → Contact provider

Machine-readable spec so AI agents can integrate this API.

/api/wordpress-api/openapi.json
/api/wordpress-api/llms.txt

Discovery: GET /api/index.json lists every API.

API health

healthy
Uptime
100.00%
Server probes · 24h
Avg latency
450 ms
Server probes · 24h
Subscribers
3,638
active
Total calls
102
last 7 days
status Full status page → · 16 probes/24h

Pricing

Pick a tier — billed monthly, cancel anytime.

Free

Free

  • 3,640 calls / month
  • 2 requests / second
  • Hard cap (429 above quota, no overage)
  • 3,640 calls/month
  • 2 req/sec
  • Plugin + theme + search
  • No credit card
Sign in to subscribe

Starter

€4.45 /month

  • 49,000 calls / month
  • 8 requests / second
  • Hard cap (429 above quota, no overage)
  • 49k calls/month
  • 8 req/sec
  • Install counts + WP/PHP requirements
  • Email support
Sign in to subscribe

Pro

€13.25 /month

  • 240,000 calls / month
  • 20 requests / second
  • Hard cap (429 above quota, no overage)
  • 240k calls/month
  • 20 req/sec
  • Dashboards / update tooling
  • Priority support
Sign in to subscribe

Mega

€35.05 /month

  • 1,210,000 calls / month
  • 50 requests / second
  • Hard cap (429 above quota, no overage)
  • 1.21M calls/month
  • 50 req/sec
  • WordPress-data platform
  • Dedicated SLA
Sign in to subscribe

Built by

P
PremiumApi

Related APIs

Other APIs with overlapping tags.

US Hospitals API

Search and filter more than 5,400 Medicare-certified hospitals across the United States and territories: filter by state, city, free-text name, hospital type (acute care, critical access, psychiatric, childrens, veterans and more), ownership category, whether the hospital offers emergency services, and the CMS overall star rating. Look up any hospital by its CMS facility id, and read metadata listing every state with its hospital count plus the available types and ownership categories for building filter UIs. Each record returns the facility id, name, full address, county, phone number, type, ownership, emergency-services flag and overall rating. Built on the official CMS Hospital General Information dataset. Every endpoint accepts input via the query string or the request body and returns lean JSON. Pure server-side data (no third-party upstream), so responses are instant and always available. Ideal for healthcare directories, patient-facing apps, insurance and care-navigation tools, and research.

api.oanor.com/hospitals-api

Sitemap API

Fetch and parse an XML sitemap (the sitemaps.org protocol). Pass a sitemap URL and the parse endpoint fetches it — following redirects and transparently gunzipping .gz sitemaps — and returns its type: a urlset with every URL and its lastmod, changefreq and priority, or a sitemapindex listing the child sitemaps, with offset/limit paging for large files. The urls endpoint goes further: when the sitemap is an index it fetches the child sitemaps too and flattens every page URL into a single list, with a configurable cap on URLs and child sitemaps and a truncated flag so you stay in control. The request is made server-side and private or internal targets are refused (SSRF-guarded). Built for SEO audits, building crawl queues and content inventories, change monitoring and migration checks. A sitemap fetcher and parser — distinct from generic XML-to-JSON conversion (xml), the robots.txt evaluator (robots) and the on-page SEO audit (seo). No upstream key, no cache.

api.oanor.com/sitemap-api

Text Segmentation API

Count and split text the way people actually read it, using Unicode-correct segmentation. The count endpoint returns the number of grapheme clusters — the real, user-perceived characters, so a family emoji counts as 1 (not 7) and an accented letter as 1 — alongside words, sentences, code points, UTF-16 code units (the naive string length that over-counts) and UTF-8 byte length. This is exactly what character-limit fields, tweet/SMS counters and validation need so the count agrees with what the user sees. The segment endpoint splits text into grapheme, word or sentence segments (word segments are flagged word-like versus punctuation and spaces) and is locale-aware, so Japanese, Chinese and Thai word boundaries come out right. Everything is computed locally with no network calls. A Unicode text segmenter — distinct from the Unicode codepoint database (unicode), the case/text-utilities toolkit (text) and string similarity (similarity). No upstream key, no cache.

api.oanor.com/segmenter-api

Localized Names API

Get the localized display name of a code in any language — countries and regions, languages, currencies, scripts and calendars. Pass a code, a type and a locale and the name endpoint returns the right name: US as region in fr gives "États-Unis", de as language in fr gives "allemand", EUR as currency gives "Euro", and the same code reads correctly in German, Japanese, Arabic or any other locale. The list endpoint returns every code of a type localized and sorted in that locale's collation — ideal for building a country, language or currency dropdown in any language. Powered by the platform's full ICU data (Intl.DisplayNames) and computed locally with no network calls. Built for internationalised forms and pickers, multilingual UIs, localized reports and onboarding. A localized-names resolver — distinct from country reference data in English (countries), number and currency formatting (numberformat) and locale date formatting (datelocale). No upstream key, no cache.

api.oanor.com/displaynames-api

Frequently asked questions

Quick answers about pricing, quotas, and integration.

How do I get an API key for WordPress Directory API?
Sign up for free at oanor.com, generate an API key from the developer dashboard, and call WordPress Directory API with the x-oanor-key header. No credit card needed for the free tier.
What's the rate limit for WordPress Directory API?
Free tier allows 1 request per second. Paid plans scale up to 50 requests per second on the Mega tier. Hard limits return HTTP 429 above the quota — no surprise overage charges.
How much does WordPress Directory API cost?
WordPress Directory API has a free tier with 100 calls / month. Paid plans start at €4.45 / month with higher quotas and faster rate limits.
Can I cancel my subscription anytime?
Yes. Plans are billed monthly and you can cancel anytime from your billing dashboard. No long-term contracts and no cancellation fee.
Is WordPress Directory API GDPR-compliant?
All requests to WordPress Directory API go through our EU-based gateway. Your upstream API key never leaves our server and no personal data is shared with the upstream provider beyond the request you send.

Pick an endpoint from the list on the left to see its details and try it.

Code snippets

Sign up to get an API key, then call any path under your slug.

curl https://api.oanor.com/wordpress-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/wordpress-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/wordpress-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
    "https://api.oanor.com/wordpress-api/SOME_PATH",
    headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())

Ratings

Sign in to rate.

No reviews yet.

Discussion

Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.

Sign in to start a thread or reply.

Sign in

New thread

/ 4000

📌 Pinned 🔒 Locked

·

· ·

/ 4000

🔒 This thread is locked — no new replies.

  • No threads yet — start the discussion.

Support

Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.

Sign in to open a support ticket.

Sign in

Open new ticket

Describe what you need help with. The provider team gets an email and replies on the ticket page.

  • No tickets yet for this API.

Subscription active — calls can start immediately.

Send your first request —

Subscription active — copy a snippet and fire off your first call.