{"action":"created","issue":{"url":"https://api.github.com/repos/cfpb/back-end/issues/3","repository_url":"https://api.github.com/repos/cfpb/back-end","labels_url":"https://api.github.com/repos/cfpb/back-end/issues/3/labels{/name}","comments_url":"https://api.github.com/repos/cfpb/back-end/issues/3/comments","events_url":"https://api.github.com/repos/cfpb/back-end/issues/3/events","html_url":"https://github.com/cfpb/back-end/issues/3","id":101515050,"number":3,"title":"API Design ","user":{"login":"willbarton","id":10562538,"avatar_url":"https://avatars.githubusercontent.com/u/10562538?v=3","gravatar_id":"","url":"https://api.github.com/users/willbarton","html_url":"https://github.com/willbarton","followers_url":"https://api.github.com/users/willbarton/followers","following_url":"https://api.github.com/users/willbarton/following{/other_user}","gists_url":"https://api.github.com/users/willbarton/gists{/gist_id}","starred_url":"https://api.github.com/users/willbarton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/willbarton/subscriptions","organizations_url":"https://api.github.com/users/willbarton/orgs","repos_url":"https://api.github.com/users/willbarton/repos","events_url":"https://api.github.com/users/willbarton/events{/privacy}","received_events_url":"https://api.github.com/users/willbarton/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":19,"created_at":"2015-08-17T21:35:27Z","updated_at":"2016-07-26T13:24:54Z","closed_at":null,"body":"How do we generally design our APIs? How do they return data from different methods (GET, POST, PUT, etc)? How do they error? How do we secure our writable APIs?\r\n\r\nThese are all the questions I have off the top of my head regarding API design that I think we should work to standardize. As far as best practices go, [I think this is a pretty good general rundown](http://www.vinaysahni.com/best-practices-for-a-pragmatic-restful-api)."},"comment":{"url":"https://api.github.com/repos/cfpb/back-end/issues/comments/235266009","html_url":"https://github.com/cfpb/back-end/issues/3#issuecomment-235266009","issue_url":"https://api.github.com/repos/cfpb/back-end/issues/3","id":235266009,"user":{"login":"willbarton","id":10562538,"avatar_url":"https://avatars.githubusercontent.com/u/10562538?v=3","gravatar_id":"","url":"https://api.github.com/users/willbarton","html_url":"https://github.com/willbarton","followers_url":"https://api.github.com/users/willbarton/followers","following_url":"https://api.github.com/users/willbarton/following{/other_user}","gists_url":"https://api.github.com/users/willbarton/gists{/gist_id}","starred_url":"https://api.github.com/users/willbarton/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/willbarton/subscriptions","organizations_url":"https://api.github.com/users/willbarton/orgs","repos_url":"https://api.github.com/users/willbarton/repos","events_url":"https://api.github.com/users/willbarton/events{/privacy}","received_events_url":"https://api.github.com/users/willbarton/received_events","type":"User","site_admin":false},"created_at":"2016-07-26T13:24:54Z","updated_at":"2016-07-26T13:24:54Z","body":"> I guess, the guideline might be: Use the full expressive power of HTTP status codes to describe success and failure states.\r\n\r\nGreat big ol' 👍 "}}
{"actor":{"display_login":"willbarton"}}