# WP REST API Explorer

> Check WordPress sites through their REST API, read-only and via your local proxy: routes, content, plugins, diagnosis, a security check and reports.

Source: https://www.jpkc.com/db/en/tools/wp-api/

## What a WordPress site gives away through its API

Every WordPress installation ships with a REST API, and by default it is open to visitors who are not logged in. Through it, anyone can read posts, pages, media, categories and often user names too — plus every route that plugins and the theme add on top. The [WP REST API Explorer](https://www.jpkc.com/tools/wp-api/) shows you what a site actually exposes there: how the API is found, whether it works, how much content is readable, which plugins, theme and WordPress version can be recognised from outside — and whether any of that reveals data that shouldn't be public.

You enter an address and click **Check site**. The check works through the site in phases, and when it's done, the **Quick Check** tab sums up the result in plain language. Everything else — routes, content, findings, reports — waits in tabs of its own.

The tool is made for **WordPress developers** who take over a site or want to x-ray one before go-live, for **agencies** that want to hand their clients a report they can actually understand, and for anyone who **hardens** a site and then wants to verify that the measures work. Only check sites you own or are allowed to test — the tool itself says so, too.

## Read-only, and only through your local proxy

In one respect the Explorer differs fundamentally from the other JPKCom tools: it works **exclusively through the free local JPKCom proxy** (localproxy) running on your own computer. There is no server-side proxy and no detour via jpkc.com — the tool page's Content Security Policy allows connections only to its own server and to `127.0.0.1` or `localhost`, that is, to your proxy. That has consequences:

- **Requests come from your computer and your IP address.** If a firewall blocks the check, it's your IP that gets blocked.
- **The tool only reads.** It sends nothing but `GET` and `HEAD` requests and changes nothing on the site it checks.
- **Proxy version:** you need localproxy **1.3.0 or newer**. Checks **with a login** (application password or JWT) and **local sites** — DDEV, wp-env, intranet — need **1.4.0**.
- **Credentials stay in the page's memory.** They never end up in browser storage, links, reports or exports; reloading the page forgets them.

A four-step guide — download, start, allow local network access in the browser, connect — sits right inside the tool. On first contact your browser (Chrome, for instance) may ask whether the page may access devices on your local network; choose **Allow**.

## The twelve tabs at a glance

- **Quick Check** — the summary for everyone: a headline sentence, findings by level, a short diagnosis when something stands out, and "Site at a glance" with API, content, plugins, theme and version.
- **Overview** — site name, addresses, time zone, front page, estimated WordPress version, the API's namespaces and a content inventory with exact counts per content type, plus a publication timeline.
- **Content** — posts, pages, custom post types, media, terms, comments and authors as filterable lists in four views, with a detail view, charts and a full pull on request.
- **Structure** — every route by namespace, with methods, arguments, schema and the status it returned during the run; plus a request form with curl, fetch and PHP snippets.
- **Search** — full-text search across all loaded data, the site's own search and the search of individual lists.
- **Plugins & Theme** — what can be recognised from outside about plugins and theme, with confidence and the signals behind it; with a login, the real plugin list.
- **Diagnosis** — why the site answers the way it does: a verdict such as "Front end broken, API fine." with a next step and the requests as evidence.
- **Security** — what anonymous visitors can read through the API: findings with level, confidence and evidence, up to eleven targeted test requests, a pattern scan for e-mail addresses, IBANs and keys, and hardening snippets to apply.
- **Reports** — a technical report and a customer report built from the same data, as Markdown or as a ZIP pack.
- **Export** — the loaded data as JSON, CSV, Markdown for AI tools or ZIP, plus the API description as OpenAPI 3.1.
- **Snapshots** — save the state of a check as a file, reopen it later without a single request, or compare it with newer data.
- **Reference** — a cheat sheet for the WordPress REST API: core concepts, authentication, global parameters, status codes and how to read the results.

## Honest results instead of an overall grade

The security part gives **no overall score**. Every finding carries one of four levels — *Action needed*, *Worth reviewing*, *Good to know*, *OK* — plus whether it is **confirmed** (seen in a response) or **likely** (derived from a reliable but indirect signal). *Action needed* appears only when the tool actually sees non-public data, such as other people's contact details or a secret key. Anything that could not be checked is labelled **Not checked** — with a reason, and never as "OK". When a result rests on a sample, the tool says that too.

Where a finding has a fix, the Security tab links the matching snippet in the [WP Code Generator](https://www.jpkc.com/db/en/tools/wp/) via "Open the matching snippet: …" — "Hide users REST endpoint from visitors" or "Disable XML-RPC", for example. Apply it, then check again.

## Try it now

**[→ Open the WP REST API Explorer](https://www.jpkc.com/tools/wp-api/)** — start the proxy, connect, enter an address, click *Check site*. Free, no account needed; the proxy is open source.

## Related JPKCom tools

- **[WP Code Generator](https://www.jpkc.com/db/en/tools/wp/)** — supplies the hardening snippets the Security tab points to, as a must-use plugin or for `functions.php`.
- **[SEO & GEO Analyzer](https://www.jpkc.com/db/en/tools/seo/)** — rates HTTP security headers, TLS and a page's SEO side; the Explorer deliberately doesn't.
- **[DNS, SSL, Redirect & URL](https://www.jpkc.com/db/en/tools/dns-ssl-redirect-url/)** — when the diagnosis reports certificate or redirect problems, dig into them there.
- **[JSON Editor](https://www.jpkc.com/db/en/tools/json/)** and **[CSV Editor](https://www.jpkc.com/db/en/tools/csv/)** — for working with the exports.
- **[localproxy — Guide & Tips](https://www.jpkc.com/db/en/guides/proxy-jpkcom-dev-tools/)** — background on downloading, starting and configuring the proxy; what the Explorer needs from it is covered in the manual.

---

The subpages go deeper: the **[Manual](https://www.jpkc.com/db/en/tools/wp-api/manual/)** covers setup, the check run and every tab in detail, the **[Examples](https://www.jpkc.com/db/en/tools/wp-api/examples/)** walk through real workflows, and **[Tips & Tricks](https://www.jpkc.com/db/en/tools/wp-api/tips/)** collects the finer points.

## In this section

- [Manual](https://www.jpkc.com/db/en/tools/wp-api/manual.md): The WP REST API Explorer in detail: proxy setup, the check run and request limit, logins, all twelve tabs from Quick Check to Snapshots, and the limits.
- [Examples](https://www.jpkc.com/db/en/tools/wp-api/examples.md): Hands-on runs with the WP REST API Explorer: a first check, a DDEV site before go-live, closing user enumeration, a login test and a client report.
- [Tips & Tricks](https://www.jpkc.com/db/en/tools/wp-api/tips.md): Tricks for the WP REST API Explorer: reading findings right, the request limit and IP blocks, proxy pitfalls, login tests and pairing it with other tools.
