WP REST API Explorer by

Local proxy

Local proxy: not connected

This tool works only with the free local JPKCom proxy. The proxy runs on your computer and sends every request to the site you check from there — nothing goes through jpkc.com. The tool only reads (GET and HEAD) and never changes anything on the site.

  1. 1 Download the proxy

    Download the file for your system from the GitHub releases of the JPKCom proxy (free, open source, GPL-2.0-or-later). Version 1.3.0 or newer is needed. Checks with a login and checks of local sites need 1.4.0 or newer.

    SystemFile
    Windows (x64)localproxy-windows-amd64.exe
    macOS Apple Silicon (macOS 13 or newer)localproxy-macos-apple-silicon
    macOS Intel (macOS 13 or newer)localproxy-macos-intel
    Linux / WSL (x64, ARM64)localproxy-linux-amd64, localproxy-linux-arm64
    FreeBSD, OpenBSD, NetBSDlocalproxy-freebsd-amd64, localproxy-freebsd-arm64, localproxy-openbsd-amd64, localproxy-netbsd-amd64
  2. 2 Start it for this site

    Open a terminal in the download folder and start the proxy with the command for your system. --origin lets only this site use it. Keep the window open while you use the tool.

    Windows

    SmartScreen: if Windows shows “Windows protected your PC”, choose More info → Run anyway. The file is not signed.

    PowerShell (in the download folder):

    .\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765

    Command Prompt (cmd.exe):

    localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765

    To start it by double-click, create a file start-localproxy.cmd next to the proxy with these two lines (without them, a double-click starts the proxy on a random port and for every site):

    cd /d "%~dp0"
    localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765

    Optional

    Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:

    .\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"
    • Several DDEV sites at once: --allow-local "*.ddev.site" — allows every local DDEV project; only if all of them may be checked.
    • Large sites: --timeout 60
    • Intranet names: --dns system plus the network range, e.g. --allow-local "wp.intranet.example,10.0.5.0/24"
    • wp-env: --allow-local "localhost:8888"
    • DDEV sites over https: run mkcert -install on this computer.

    Fixed token (optional; otherwise the token changes on every start):

    .\localproxy-windows-amd64.exe --origin "https://www.jpkc.com" --port 8765 --token-file "$env:LOCALAPPDATA\localproxy\token"

    In cmd.exe the token file is --token-file "%LOCALAPPDATA%\localproxy\token".

    macOS

    Gatekeeper: the file is not signed, so macOS blocks it at first. Make it executable, remove the quarantine flag and give it a short name (Intel Macs: use localproxy-macos-intel instead). macOS 13 Ventura or newer is needed.

    chmod +x ./localproxy-macos-apple-silicon
    xattr -dr com.apple.quarantine ./localproxy-macos-apple-silicon
    mv ./localproxy-macos-apple-silicon ./localproxy

    Start:

    ./localproxy --origin "https://www.jpkc.com" --port 8765

    If macOS still refuses: System Settings → Privacy & Security → Open Anyway.

    Optional

    Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:

    ./localproxy --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"
    • Several DDEV sites at once: --allow-local "*.ddev.site" — allows every local DDEV project; only if all of them may be checked.
    • Large sites: --timeout 60
    • Intranet names: --dns system plus the network range, e.g. --allow-local "wp.intranet.example,10.0.5.0/24"
    • wp-env: --allow-local "localhost:8888"
    • DDEV sites over https: run mkcert -install on this computer.

    Fixed token (optional; otherwise the token changes on every start):

    ./localproxy --origin "https://www.jpkc.com" --port 8765 --token-file "$HOME/.config/localproxy/token"

    Linux / WSL

    Make the file executable and give it a short name (ARM64: localproxy-linux-arm64):

    chmod +x ./localproxy-linux-amd64
    mv ./localproxy-linux-amd64 ./localproxy

    Start:

    ./localproxy --origin "https://www.jpkc.com" --port 8765

    Optional

    Local sites (DDEV, localhost, intranet; needs localproxy 1.4.0 or newer) — allow exactly the site you check:

    ./localproxy --origin "https://www.jpkc.com" --port 8765 --allow-local "your-site.ddev.site"
    • Several DDEV sites at once: --allow-local "*.ddev.site" — allows every local DDEV project; only if all of them may be checked.
    • Large sites: --timeout 60
    • Intranet names: --dns system plus the network range, e.g. --allow-local "wp.intranet.example,10.0.5.0/24"
    • wp-env: --allow-local "localhost:8888"
    • DDEV sites over https: run mkcert -install on this computer.

    Fixed token (optional; otherwise the token changes on every start):

    ./localproxy --origin "https://www.jpkc.com" --port 8765 --token-file "$HOME/.config/localproxy/token"

    The proxy prints its address and a token in a box (lines Address and Token). The token is new on every start — after a restart, enter it again in step 4.

  3. 3 Allow access to your local network

    When the tool contacts the proxy for the first time, your browser may ask whether this site may access devices on your local network. Choose Allow. The request that made the browser ask always fails, even after “Allow” — the tool checks again by itself after a moment, or press Check again.

    If you blocked it by mistake, change it in the site settings of your browser (names may differ slightly between versions):

    • Chrome: Settings → Privacy and security → Site settings → View permissions and data stored across sites → this site → Local network access
    • Brave: Settings → Privacy and security → Site and Shields Settings → All sites → this site → Local network
  4. 4 Connect

    Copy the address and the token from the proxy window.

    Only the lines Address and Token are read; nothing else is taken over.

    Address and token are saved in this browser and shared with the other proxy tools on this site (Expert Mode).

Site to check

Only check sites you own or are allowed to test. The requests come from your computer and your IP address.

Run settings

Content
Not part of the check yet: load all items per collection in the Content tab.

Counted in requests to the site (one proxy call can be several site requests), for the whole check: the run and every click after it. Short bursts at the rate above, never more than 60 per minute; a full pull in the Content tab shows its cost before it starts.

This check also sends these requests

In the addresses: <home> = the site's home page, <url> = the WordPress address (where WordPress is installed), <api> = the REST API root (e.g. …/wp-json).

  • The list appears once the tool has loaded.

The real addresses are known only after the first requests. Every probe is an anonymous GET request, counts toward the request limit and appears in the request log.

Only the address (without query) is kept in this browser. Turning this off clears the list.

Credentials

Locked: needs local proxy 1.4.0 or newer.

Credentials
Apply works after a first check of this site without a login.

  • First check the site without a login, then apply. The next Check site also runs the checks with your login.
  • Credentials are never saved: not in this browser, not in links, reports or exports. Reloading the page forgets them.
  • They are only sent to the exact site you entered, and only for read requests.
  • Your browser may offer to save this password — choose Never.

Request log

No requests yet.

A dot on a tab: part of its data is missing.

Quick Check

Enter a site address and press Check site.

One click checks what the WordPress REST API of a site shows to anonymous visitors, in plain language: how the API is found, whether it works as expected, how much content can be read, and which plugins, theme and WordPress version can be seen from outside.

Overview

Enter a site address and press Check site.

Site name and description, WordPress and home address, time zone, an estimate of the WordPress version, namespaces (core or plugin) and the number of entries per content type.

Content

Enter a site address and press Check site.

Posts, pages, custom post types, media, terms, comments and authors: counts first, then a sample. Lists with filters, sorting and four views (visual, table, JSON tree, raw).

Links

Links under the site's API open here as one request; other links open directly in your browser, not via the proxy.

Structure

Enter a site address and press Check site.

All routes by namespace with methods, arguments, schema and whether they answered without login during the check.

Plugins & Theme

Without a login, WordPress gives out no plugin data. This tab shows what can be recognised from outside. The real number of plugins can be higher: a plugin is only recognised by a trace it leaves, for example a file it loads on the home page.

Enter a site address and press Check site.

Plugins and the theme that can be recognised from outside, with confidence and the signals behind it, and the WordPress version as “at least x.y”.

Diagnosis

Enter a site address and press Check site.

Why the site answers the way it does: home page, REST discovery, index and content, with a verdict and the next steps.

Security

Enter a site address and press Check site.

What anonymous visitors can read through the API: findings with level, confidence and evidence, the evidence probes that were sent, and the checks that could not run.

Reports

Enter a site address and press Check site.

A technical report and a report for your client, both from the same data, to copy or download as Markdown.

Export

Enter a site address and press Check site.

The loaded data as JSON, CSV, Markdown or ZIP, and the API description as an OpenAPI 3.1 document.

Snapshots

A snapshot is a file with the data of a check. It stays on your computer. Open it later without a request to the site, or compare it with newer data.

Save a snapshot

Without it the file stays small. Changed text is still noticed, but the words can't be shown.

Open a snapshot

The file is checked first. If the check fails, nothing changes. Otherwise all views show the file, and nothing is sent, not even to the local proxy.

Compare

Compares two states of the same site. Nothing is loaded for this. An entry only counts as added, removed or resolved if both sides really saw it. Everything else says “not comparable”, with the reason.

Compare with

Reference

As of WordPress 7.1 · REST API Handbook

REST basics

  • Namespace — a group of routes, e.g. wp/v2 (core) or myplugin/v1.
  • Route — a path below the API root, e.g. /wp/v2/posts; an endpoint is a route plus a method.
  • Collection (/wp/v2/posts) vs. item (/wp/v2/posts/12); _links point to related resources.
  • The API root is announced in the Link header (rel="https://api.w.org/"); usually /wp-json/, with plain permalinks ?rest_route=/.

Authentication

  • Anonymous — what every visitor sees; the default of this tool.
  • Application password (Basic) — HTTPS only, except for local sites.
  • JWT (Bearer) — only with a JWT plugin. The plugins hand out tokens via POST; this tool never sends POST, so you paste a token you created elsewhere.
  • Cookie + nonce — only inside a logged-in browser; not usable by this tool.
  • This tool only reads (GET and HEAD). Logins need localproxy 1.4.0.

Global parameters

ParameterExample
context?context=view (also embed, edit with login)
_fields?_fields=id,title,link
_embed?_embed=author
per_page / page?per_page=100&page=2 (max. 100)
_envelope?_envelope — status and headers inside the body

X-WP-Total and X-WP-TotalPages give the totals. Entries are filtered after counting, so a short or empty page does not mean the list is finished.

Status codes

200OK
400Invalid parameter (rest_invalid_param, rest_post_invalid_page_number)
401Login needed (rest_forbidden, rest_not_logged_in)
403Logged in without permission — or the HTML page of a firewall
404No such route (rest_no_route)
429Too many requests
500PHP error (internal_server_error)
503Maintenance mode
502 / 504From the proxy, not the site (no X-Upstream-Protocol)

How to read results

Findings use four levels, always with a word, never only a colour: Action needed Worth reviewing Good to know OK. Each finding says whether it is confirmed or likely and shows its evidence. There is no overall grade. A check that could not run says “Not checked” with the reason — never “OK”.

Results from a sample say so (“based on 240 of 18 312 items”). Absence of a finding in a sample is not proof that the whole site is clean.