Could any of the seasoned parse server developers please explain what is the difference between the Parse Server REST API documented here: REST API Guide | Parse and the Parse Server Public API described here: parse-server/PublicAPI.spec.js at master · parse-community/parse-server · GitHub?
From what I understand, invoking REST API goes via parse server top level mount path like
https://myserver/parse, and each HTTP(s) request requires presence of
X-Parse-REST-API-Key. Body is supplied as JSON.
Based on the supplied
appid, the request is routed to a proper app, potentially running at the same mount path (functionality used by original facebook implementation in the past but now largely redundant thanks to docker containerization).
The public API on the other hand resides at
/appid, like this:
https://myserver/parse/apps/appid and it’s requires body supplied as form data.
The public API for now exposes endpoints to
- verify user’s email
- change user’s password based on token previously requested via REST API
- reset verification email
- ?? other ??
I wonder why these two are separate and whether they could potentially be merged?