{"action":"opened","issue":{"url":"https://api.github.com/repos/ZenHubIO/support/issues/811","repository_url":"https://api.github.com/repos/ZenHubIO/support","labels_url":"https://api.github.com/repos/ZenHubIO/support/issues/811/labels{/name}","comments_url":"https://api.github.com/repos/ZenHubIO/support/issues/811/comments","events_url":"https://api.github.com/repos/ZenHubIO/support/issues/811/events","html_url":"https://github.com/ZenHubIO/support/issues/811","id":163052527,"number":811,"title":"As a user, I want to consume data via webhooks vs a strict API","user":{"login":"thomasrockhu","id":4213028,"avatar_url":"https://avatars.githubusercontent.com/u/4213028?v=3","gravatar_id":"","url":"https://api.github.com/users/thomasrockhu","html_url":"https://github.com/thomasrockhu","followers_url":"https://api.github.com/users/thomasrockhu/followers","following_url":"https://api.github.com/users/thomasrockhu/following{/other_user}","gists_url":"https://api.github.com/users/thomasrockhu/gists{/gist_id}","starred_url":"https://api.github.com/users/thomasrockhu/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/thomasrockhu/subscriptions","organizations_url":"https://api.github.com/users/thomasrockhu/orgs","repos_url":"https://api.github.com/users/thomasrockhu/repos","events_url":"https://api.github.com/users/thomasrockhu/events{/privacy}","received_events_url":"https://api.github.com/users/thomasrockhu/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2016-06-29T23:48:22Z","updated_at":"2016-06-29T23:48:22Z","closed_at":null,"body":"The API is very good regarding retrieving data about my boards and issues, but I want to be able to receive JSON to a callback URL whenever I an event has occurred (e.g. an issue has been moved to a new pipeline).\r\n\r\nHaving webhooks helps me from running a script every `x` minutes to discover what issues may have been moved around, which can be very costly in terms of # requests being made (and thus hitting the rate limiting barrier) "}}
{"actor":{"display_login":"thomasrockhu"}}