Get a webhook for a workspace
Returns the webhook with the specified id installed on the given workspace.
Authorizations
Section titled “ Authorizations ”Parameters
Section titled “ Parameters ”Path Parameters
Section titled “ Path Parameters ”Installed webhook’s ID
This can either be the workspace ID (slug) or the workspace UUID
surrounded by curly-braces, for example: {workspace UUID}.
Responses
Section titled “ Responses ”The webhook subscription object.
object
The webhook’s id
The URL events get delivered to.
A user-defined description of the webhook.
The type of entity. Set to either repository or workspace based on where the subscription is defined.
Base type for most resource objects. It defines the common type element that identifies an object’s type. It also identifies the element as Swagger’s discriminator.
object
The events this webhook is subscribed to.
Indicates whether or not the hook has an associated secret. It is not possible to see the hook’s secret. This field is ignored during updates.
The secret to associate with the hook. The secret is never returned via the API. As such, this field is only used during updates. The secret can be set to null or “” to remove the secret (or create a hook with no secret). Leaving out the secret field during updates will leave the secret unchanged. Leaving out the secret during creation will create a hook with no secret.
Example
{ "subject_type": "repository", "events": [ "issue:comment_created" ]}If the webhook or workspace does not exist.
Base type for most resource objects. It defines the common type element that identifies an object’s type. It also identifies the element as Swagger’s discriminator.
object
object
Optional structured data that is endpoint-specific.
object
Example generated
{ "type": "example", "error": { "message": "example", "detail": "example", "data": {} }}