Sapling’s API can provide other services, but I’m wondering if these functionalities would suffice for a first interaction? It is enough for my current use case.
I think this may be interesting for more users in the future, besides the documentation on Creating your first node, is there anything else I should keep in mind to have my node approved when the time comes?
I plan to create workflows to setup all systems and accounts for new developers using this Sapling’s node as source.
I just had a quick look at the API. We usually add all the CRUD operations per resource. So, it will be cool if you can add the create and update as well.
We are working on a PR template (checklist) that you can go through to make sure your PR has everything needed to be approved. In the meantime, you can add the create and update operations and send the PR. I will have a look at it.