Black Friday Sale is Live: Get up to 30% OFF RankReady Pro - the WordPress AI SEO pluginBlack Friday Sale is Live: Up to 30% OFF Get Deal
Features

The hatch/v1 REST bridge, explained

How the hatch/v1 REST API shares WordPress content with your frontend: what it exposes, how to read it, and how it relates to the core WordPress REST API.

Last updated November 4, 2026

Hatch shares your content with the frontend through a REST API under the hatch/v1 namespace. It sits next to the core WordPress REST API and returns data already shaped for a frontend. You can also build your own frontend against it.

Where it lives

https://your-site.com/wp-json/hatch/v1/

Opening that address lists every route Hatch registers. An easy test is the features route:

curl https://your-site.com/wp-json/hatch/v1/features

What it exposes

  • Content: single items, lists, the block output of a post, menus and redirects.
  • Site settings: design, features and integrations.
  • SEO data: head tags, meta and schema read from your active SEO plugin.
  • Forms and comments: reading forms, submitting them and posting comments.
  • Deploy and status: used by the dashboard to deploy, redeploy, check the connection and revalidate the cache.
  • Store (WooCommerce only): products, variations, categories and featured products under /store/.
  • Accounts (optional): sign-in, sign-up, logout, current visitor and refresh under /auth/, available only when Frontend accounts is on.

The full list, with who can call each route, is in Every Hatch endpoint, referenced. Read routes are public. Routes that change settings, deploy or trigger outbound requests need an administrator. Form, comment and sign-in submissions are open by design and protected by nonces, keys and rate limits.

Access and safety

  • The frontend reads as a dedicated Subscriber account that you create. Hatch checks it refuses any account that can edit others’ posts or manage the site, both when you enter it and each time it signs in.
  • The Lock the REST API switch on the Security tab closes the core data feed to signed-out visitors while a short list of routes the frontend needs stays open.
  • The hatch/v1/auth routes do not exist until you switch on Frontend accounts.

REST only

The bridge carries data, not code. Nothing from your WordPress plugins’ CSS or JavaScript is sent to the frontend.

What to do next

If a route returns 404, see The REST API returns 404.