New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WIP - Extend API #717
WIP - Extend API #717
Conversation
I've prepared a stage. Click to open. |
Awesome. It's great to see some work being done in this area. Can you describe a bit more of what you'd like to change and why? Do you have bigger plans for the API, or is this the extent of what you need? |
The goal would be to have the ability to:
And potentially more. I’d also like to add documentation on how to use the API. In addition, I’d like to create an overall API key, API secret to generate a token to be used as an authentication mechanism for the API. I really like how each app has its own key, but I think its potentially a better idea to secure requests via a token for authenticated api requests. And SSL the entire api. The reason for doing all this work is to enable other developers to build integrations based off of the errbit data. Its a lofty project but I think its definitely worth it. I’d love to continue to have this conversation and hear yours and others ideas on how to best approach this. On Aug 13, 2014, at 3:09 PM, Stephen Crosby notifications@github.com wrote:
|
This reverts commit 8cf7649.
Messed up here in this PR. Gonna close this WIP PR and do another one. |
This PR is a WIP to extend the API to allow more endpoints. Also will need to follow up with API documentation. Let's discuss!