As I am trying to integrate Ergo more and more into my website it would be nice to have API endpoints to manipulate the user data stored in the Ergo database.
With this it would be possible to present an easy to use webinterface where people can change their email address and other detail (password is already possible).
For the implementation into the API I could imagine two ways:
Either expose each "field" seperately like /api/v1/ns/saset/email and so on.
Or have the endpoint called v1/ns/saset and POST the keys and values as JSON. With the latter Ergo could accept known fields and ignore unknown.
Something similar would also be nice for channel manipulation later.
As I am trying to integrate Ergo more and more into my website it would be nice to have API endpoints to manipulate the user data stored in the Ergo database.
With this it would be possible to present an easy to use webinterface where people can change their email address and other detail (password is already possible).
For the implementation into the API I could imagine two ways:
Either expose each "field" seperately like /api/v1/ns/saset/email and so on.
Or have the endpoint called v1/ns/saset and POST the keys and values as JSON. With the latter Ergo could accept known fields and ignore unknown.
Something similar would also be nice for channel manipulation later.