At the moment the Netlify CMS API errors are a little vague, it’s a work in progress. Most of these issues have been posted here before, but I think it’d be useful to have an overview because they all look pretty much alike:
API_ERROR: {"message":"404 File Not Found"}
As far as I know there are two scenarios that cause this error:
- The collection
folderorfileproperty is missing a value (a dedicated file or folder, can’t be blank or root). The file or folder should be relative to root (sosrc/postsfor example). - There are subfolders within the collection folder
API_ERROR: Not Found
- The media library folder is missing, or the value of the media library property within
config.ymlisn’t correct.
Failed to load entries: API_ERROR: Not Found
- Git Gateway is not enabled: Enable Git Gateway from the Netlify Identity settings or refresh the token
- There aren’t any entries for a given collection. Nothing serious, if you add content the error will go away.
Failed to load entry: API_ERROR: Not Found
- The collection
folderorfileproperty is missing a value (a dedicated file or folder, can’t be blank or root). The file or folder should be relative to root (sosrc/postsfor example). - There aren’t any entries for a given collection. Nothing serious, if you add content the error will go away.
Failed to persist entry: API_ERROR: Not Found
- The org account needs to grant access to your Netlify CMS instance: https://help.github.com/en/github/setting-up-and-managing-your-github-user-account/requesting-organization-approval-for-oauth-apps
Not really an API error but pretty easy to resolve:
Failed to load settings from /.netlify/identity
- Netlify Identity isn’t enabled
-
config.ymlhas git-gateway as a backend on a site that isn’t hosted on Netlify