WordPress plugin search

GET https://api.api.sh/wordpress/v1/plugins
1 credit / call reference try it in the playground →

Plugins in the WordPress.org directory by keyword, tag, author or a directory list: slug, name, link, version, author and profile handle, short description, rating (percent and stars), rating breakdown, active installs, total downloads, support threads (and resolved), required and tested WordPress versions, required PHP, required plugins, last update, date added, homepage, download link, tags, icon and business model. total is the number of matches. Pass next_page back as page; null on the last page.

Every response includes credits_used: the credits this call cost.

Parameters

nametypedescription
q string Search words. Example: seo
tag string Tag slug(s), comma-separated, e.g. ecommerce.
author string Author's wordpress.org handle, e.g. automattic.
browse popular | new | updated | top-rated | featured | beta | blocks A directory list: popular, new, updated, top-rated, featured, beta, blocks.
page integer Page number (default 1).
limit integer Results per page (default 24, max 250).

Every endpoint also takes fresh, raw, fields (see lean responses and caching).

Example

curl "https://api.api.sh/wordpress/v1/plugins?q=seo" \
  -H "x-api-key: $APISH_KEY"

Response

A JSON object with the fields described above, plus raw (the source's own data), cached, fetched_at and credits_used. Errors return {"success": false, "error": "…"} with the HTTP status (see errors). A lookup that ran but found nothing (404) costs the price above; refused calls and errors on our side are free (what's charged).

The fastest way to see the full response is the playground: it runs this endpoint with your account and shows the exact JSON.