No route was found matching the URL and request method.
“No route was found matching the URL and request method.” in WordPress: causes and what to check
# Common log entries
{"code":"rest_no_route","message":"No route was found matching the URL and request method.","data":{"status":404}}
WordPress returns this REST API error, code rest_no_route, when a request to /wp-json/ matches no registered route. Screens that call the API, including the block editor, then fail to load or save.
Which of these do you see?
The rewrite rules do not pass the request to WordPress correctly, or the API is turned off.
The plugin that registers that route is inactive or failed to load.
Common causes
References
Rather not fix it yourself? Let WP119 handle it automatically.
When the REST API path is blocked or its response is polluted, the editor cannot save. This is handled automatically: the system fixes the REST path and re-verifies that the editor can save. Fixes are made on a copy of your site in the recovery station and written back only after re-verification passes. In your site’s database, the protected tables (members, comments, orders and form submissions) are copied as structure only. In SSH and FTP mode, the system creates a pre-recovery backup on your host before writing back and restores from it if verification after write-back fails. If the recovery cannot be completed, the recovery fee is refunded in full.
- Initial assessment: Site URL entry
- Copy to the recovery station: Work on a copy
- Diagnosis: Item-by-item checks
- Recovery and verification: Home and inner pages
- Write-back or delivery: Only after verification passes
Use WP119 when the block editor or the admin area fails because the REST API returns this error.
Check my site →