author_name:benbalter

We've made it even easier toknow the status of your GitHub Pages builds.Now, ifthe[`page_build`](http://developer.github.com/v3/activity/events/types/#pagebuildevent) event is enabled for a given webhook, when GitHub Pages attempts to buildyoursite following a push, yourapplication will receive an event payload containing thestatus ofthe build, and if the build resulted in an error, the error message itself.

We've made it even easier totrack the status of your[GitHub Pages](http://pages.github.com/) builds.By subscribing tothenew[`page_build`](/v3/activity/events/types/#pagebuildevent) event,your application will receive an event payload containing theresults ofeach build. (As always, these builds occur automatically following each push to a GitHub Pages-enabled branch.)

If you have the "send me everything" option selected (or use the "[wildcard event](http://developer.github.com/changes/2014-02-24-wildcard-event-for-webhooks/)" via the API), youshould receive the eventon your nextpush. Otherwise,youmust enablethe new eventon your repository's webhook settings page.

If you havea[webhook](/webhooks/) withthe["send me everything" option](https://github.com/blog/1778-webhooks-level-up) selected (orif youuse the "[wildcard event](/changes/2014-02-24-wildcard-event-for-webhooks/)" via the API), youwill receive the`page_build`eventafter the nextbuild of your GitHub Pages site. Alternatively, ifyouprefer to subscribe to specific event types, you can add tothe new`page_build`eventto yourwebhooks via yourrepository's webhook settings page or via the[webhooks API](/v3/repos/hooks/).

For more information, see[the event types documentation](http://developer.github.com/v3/activity/events/types/).

For more information, be sure to check out our guide on[working with webhooks](/webhooks/). If you have any questions or feedback, please[drop us a line][contact].

[contact]:https://github.com/contact?form%5Bsubject%5D=API+Page+Build+Event