{"action":"created","issue":{"url":"https://api.github.com/repos/SciDevs/delicious-api/issues/37","labels_url":"https://api.github.com/repos/SciDevs/delicious-api/issues/37/labels{/name}","comments_url":"https://api.github.com/repos/SciDevs/delicious-api/issues/37/comments","events_url":"https://api.github.com/repos/SciDevs/delicious-api/issues/37/events","html_url":"https://github.com/SciDevs/delicious-api/issues/37","id":60564120,"number":37,"title":"JSON response instead of XML","user":{"login":"marcoscheel","id":1809551,"avatar_url":"https://avatars.githubusercontent.com/u/1809551?v=3","gravatar_id":"","url":"https://api.github.com/users/marcoscheel","html_url":"https://github.com/marcoscheel","followers_url":"https://api.github.com/users/marcoscheel/followers","following_url":"https://api.github.com/users/marcoscheel/following{/other_user}","gists_url":"https://api.github.com/users/marcoscheel/gists{/gist_id}","starred_url":"https://api.github.com/users/marcoscheel/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/marcoscheel/subscriptions","organizations_url":"https://api.github.com/users/marcoscheel/orgs","repos_url":"https://api.github.com/users/marcoscheel/repos","events_url":"https://api.github.com/users/marcoscheel/events{/privacy}","received_events_url":"https://api.github.com/users/marcoscheel/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2015-03-10T20:28:35Z","updated_at":"2015-03-10T22:27:37Z","closed_at":null,"body":"Is there a way to get JSON repsonses instead of XML? Any planes to support this on the here documentet set of API? There is already JSON if we access the oAuth stuff, but all the traditional API is only returning XML.\r\n\r\nThank you."},"comment":{"url":"https://api.github.com/repos/SciDevs/delicious-api/issues/comments/78162247","html_url":"https://github.com/SciDevs/delicious-api/issues/37#issuecomment-78162247","issue_url":"https://api.github.com/repos/SciDevs/delicious-api/issues/37","id":78162247,"user":{"login":"peoplemerge","id":185873,"avatar_url":"https://avatars.githubusercontent.com/u/185873?v=3","gravatar_id":"","url":"https://api.github.com/users/peoplemerge","html_url":"https://github.com/peoplemerge","followers_url":"https://api.github.com/users/peoplemerge/followers","following_url":"https://api.github.com/users/peoplemerge/following{/other_user}","gists_url":"https://api.github.com/users/peoplemerge/gists{/gist_id}","starred_url":"https://api.github.com/users/peoplemerge/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/peoplemerge/subscriptions","organizations_url":"https://api.github.com/users/peoplemerge/orgs","repos_url":"https://api.github.com/users/peoplemerge/repos","events_url":"https://api.github.com/users/peoplemerge/events{/privacy}","received_events_url":"https://api.github.com/users/peoplemerge/received_events","type":"User","site_admin":false},"created_at":"2015-03-10T22:27:37Z","updated_at":"2015-03-10T22:27:37Z","body":"Yes, this is absolutely in the plans!  Most of the backend work is already done, but the documentation will come after.\r\n\r\nHint: do an inspect element on delicious.com and watch the AJAX (err AJAJson?) calls.  You might hit some CORS issues on calls that protect customer data if you want to do it all in frontend, so the work remanining is to allow oAuth paths for those."}}