webhooks

Overview

Name	Datatype	Description
`id`	`integer`	Unique identifier of the webhook.
`name`	`string`	The name of a valid service, use 'web' for a webhook.
`active`	`boolean`	Determines whether the hook is actually triggered on pushes.
`config`	`object`
`created_at`	`string`
`deliveries_url`	`string`
`events`	`array`	Determines what events the hook is triggered for. Default: ['push'].
`last_response`	`object`
`ping_url`	`string`
`test_url`	`string`
`type`	`string`
`updated_at`	`string`
`url`	`string`

Name	Accessible by	Required Params	Description
`get_webhook`	`SELECT`	`hook_id, owner, repo`	Returns a webhook configured in a repository. To get only the webhook `config` properties, see "Get a webhook configuration for a repository."
`list_webhooks`	`SELECT`	`owner, repo`	Lists webhooks for a repository. `last response` may return null if there have not been any deliveries within 30 days.
`create_webhook`	`INSERT`	`owner, repo`	Repositories can have multiple webhooks installed. Each webhook should have a unique `config`. Multiple webhooks can share the same `config` as long as those webhooks do not have any `events` that overlap.
`delete_webhook`	`DELETE`	`hook_id, owner, repo`
`ping_webhook`	`EXEC`	`hook_id, owner, repo`	This will trigger a ping event to be sent to the hook.
`test_push_webhook`	`EXEC`	`hook_id, owner, repo`	This will trigger the hook with the latest push to the current repository if the hook is subscribed to `push` events. If the hook is not subscribed to `push` events, the server will respond with 204 but no test POST will be generated. Note: Previously `/repos/:owner/:repo/hooks/:hook_id/test`
`update_webhook`	`EXEC`	`hook_id, owner, repo`	Updates a webhook configured in a repository. If you previously had a `secret` set, you must provide the same `secret` or set a new `secret` or the secret will be removed. If you are only updating individual webhook `config` properties, use "Update a webhook configuration for a repository."