4 ms·
The two biggest goals in my mind would be: 1) You involve the API consumers in the design and decision process, which helps in understanding their use cases be
by knighthacker 14y ago
The two biggest goals in my mind would be:
1) You involve the API consumers in the design and decision process, which helps in understanding their use cases better.
2) Give insights and transparency to consumers as to why and how some decisions were made about the API.
- zende 14y agoShould also be a great start to improve the API docs (https://www.balancedpayments.com/docs/api https://www.balancedpayments.com/docs/api)
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- deleted 14y ago[deleted]
- samratjp 14y agoIt'd be nice to be able fork or even comment the API docs as a developer using the API. Tooo many times I googled for an answer that the API docs neglect and found the answer instead on StackOverflow. If I had a facebook credit for every time I found the answer I was looking for with facebook's API docs, I'd be pretty poor :-p
- zende 14y ago> It'd be nice to be able fork or even comment the API docs as a developer using the API You want to comment on the API docs using the API itself? The goal is to let you fork the specs and issue a pull request on GitHub. > Tooo many times I googled for an answer that the API docs neglect and found the answer instead on StackOverflow. Are you referring to the API docs for Balanced or API docs in general?
- samratjp 14y ago(Sorry didn't realize this was actually linked to the github discussion/thought it was an Ask HN) Forking the specs sounds good. Meant the lacking in answers for API docs in general. Especially facebook in the past; though Graph Explorer is much nicer!