The REST API returns 404, and the permalinks fix

If /wp-json/hatch/v1/features returns a 404, the frontend cannot read your content. The most common cause is plain permalinks.

Fix: switch to pretty permalinks

1. In wp-admin, go to Settings, Permalinks.
2. Choose Post name (/%postname%/).
3. Click Save Changes.
4. Open /wp-json/hatch/v1/features again. It should return JSON.

The setup guide can make this change for you, and only if you tick its permalink box. Sites that already use pretty permalinks are left alone.

Still 404?

• Try the fallback form. /?rest_route=/hatch/v1/features works even with plain permalinks. If it returns JSON but the pretty URL does not, your web server rules need updating (save Permalinks again, or check your Nginx or Apache rewrite configuration).
• A security plugin or firewall may be blocking /wp-json/. Check its REST API setting.
• Lock the REST API in Hatch’s Security tab closes core routes to signed-out visitors but keeps the routes the frontend needs. If you changed it recently, turn it off to test.
• The plugin is not active. Check Plugins that Hatch Connect is activated.

Verify

Follow How to check Hatch is working once the endpoint returns JSON.