I’m using WordPress’ apiFetch library to make requests (in WordPress admin dashboard) to my WordPress REST endpoints. It looks like apiFetch will throw an error if the response is a non-2xx code, using the JSON body of the response as the error. However, it does not appear to be inserting the HTTP code anywhere in that error.
This is necessary since it allows me to differentiate between a “normal” error (like 404 if the resource asked for does not exist) and an “unexpected” error (like a 500 internal server error).
By default, apiFetch will parse the response for you automatically. You can get the raw response object by setting parse to false in the apiFetch option, e.g.:
const handleClick = async () => {
try {
const result = await apiFetch( {
path: '/your/path',
parse: false,
} );
console.log( result ) // you will see ok status (e.g. 200) in here.
} catch ( error ) {
console.log( error ); // you will see error status (e.g. 404 or 500) in here.
}
};
More info: apiFetch’s parse option
Relevant code for parsing the response: see utils/response.js in apiFetch
