At Hoodie, we are working on a hapi plugin that exposes a generic JSON API for all things account, like sign up, password reset, user management, etc. The hapi plugin will be part of the next Hoodie release, and will also be used in several eHealth projects. We are working on a client that will wrap the JSON API, too.
The JSON API spec can be found here: http://docs.accountjsonapi.apiary.io. As we are still very new to JSON API, it would be great if you could help us review it, just to make sure we don’t have any errors in reasoning. But we are happy about any kind of feedback, really
I hope this also helps others who are getting started with JSON API to see another example of how JSON API is used in real-life projects.
Open Questions (I’ll keep these up to date)
- I just found out about the JSON Patch Extension. Are the
PATCHroutes in the spec invalid as they are right now?
- I think we could make use of the Bulk Extension, too. For one, when signing up, a user should be able to create both at once, an account and a profile. On top of that, it would be nice to allow to update / remove a bulk of accounts at once