[repository-event]:/v3/activity/events/types/#repositoryevent

[membership-event]:/v3/activity/events/types/#membershipevent

[docs]:/v3/orgs/hooks/

[docs-preview]:/v3/orgs/hooks/#preview-period

[docs-preview]:/v3/orgs/hooks/

[contact]:https://github.com/contact?form[subject]=Organization+Webhooks

kind:change

title:Organization Webhooks API finalized

created_at:2015-04-21

author_name:pengwynn

After[four months in preview release][ann], the[Organization Webhooks API][docs] is now considered stable and ready for production use.

During the preview period, you needed to provide a custom media type in the`Accept` header when using the Organization Webhooks API:

Now that the preview has ended, you no longer need to pass this custom

media type, though providing an explicit[media type][media-types] is recommended:

If you have any questions or feedback on this API, please[get in touch][contact].

[ann]:/changes/2014-12-03-preview-the-new-organization-webhooks-api/

[docs]:/v3/orgs/hooks

[media-types]:/v3/media

[contact]:https://github.com/contact?form%5Bsubject%5D=Organization+Webhooks

* TOC

{:toc}

{{#tip}}

<aname="preview-period"></a>

The Organization Webhooks API is currently available for developers to preview.

During the preview period, the API may change without advance notice.

Please see the[blog post][developer-blog-post] for full details.

To access the API during the preview period, you must provide a custom[media type][media-type] in the`Accept` header:

{{/tip}}

Organization webhooks allow you to receive HTTP`POST` payloads whenever certain events happen within the organization. Subscribing to these events makes it possible to build integrations that react to actions on GitHub.com. For more information on actions you can subscribe to, check out our[Events documentation][webhook-events].