Area 05 of 11 · API & Headless
Decide who reads your content, or run WordPress behind any front end.
Control who can read your REST API, or run WordPress behind a separate front end.
Visitors get a polite refusal; logged-in users and listed routes keep working.
Choose the parts that stay open, for example forms or a shop.
(Pro) Set the front-end address; previews and links follow it.
Headless mode Pro
Makes sure no security feature gets in the way of a front end that reads content through the REST API.
The REST API is always fully open and is skipped by the firewall (blocklists, bot and attack filters, country blocking) so your front end server is never blocked. The users endpoint stays available for author names. Only your "Always block" list still applies.
The public site, e.g. https://www.example.com. Used for canonical links, social share links and the sitemap so they point to the front end instead of WordPress.
REST API access Free
The REST API (/wp-json/) lets apps and scripts read site content. By default anyone can use it.
Visitors who are not logged in can only reach the parts listed below. Logged-in users keep full access. Ignored while headless mode is on.
Route prefixes separated by spaces. The defaults keep embeds, Contact Form 7, WooCommerce blocks, Gravity Forms and Jetpack working. Add "wp/v2" to keep content readable.
Good to know
The user list endpoint is closed first: it is how bots learn your usernames.
(Pro) Pair with the REST API cache in Caching for millisecond answers.
Made by the team behind WpToHeadless.
Questions about API & Headless
No. Logged-in users always have full access.
Five minutes from now
Give your site a keel.
Steady when traffic spikes, calm when attacks come, found when people search. Start free; go Pro when a site needs more.