Update a webhook configuration for an organization

PATCH

/orgs/{org}/hooks/{hook_id}/config

Updates the webhook configuration for an organization. To update more information about the webhook, including the active state and events, use "Update an organization webhook ."

Access tokens must have the admin:org_hook scope, and GitHub Apps must have the organization_hooks:write permission.

Request Example

Shell

JavaScript

Java

Swift

curl --location --request PATCH 'https://api.github.com/orgs//hooks//config' \
--header 'Content-Type: application/json' \
--data-raw '{
    "content_type": "json",
    "insecure_ssl": "0",
    "secret": "********",
    "url": "http://example.com/webhook"
}'

Response Example

{
    "content_type": "\"json\"",
    "insecure_ssl": "\"0\"",
    "secret": "\"********\"",
    "url": "https://example.com/webhook"
}

Request

Path Params

org

string

required

The organization name. The name is not case sensitive.

hook_id

integer

required

The unique identifier of the hook.

Body Params application/json

content_type

string

optional

The media type used to serialize the payloads. Supported values include json and form. The default is form.

Example:

"json"

insecure_ssl

webhook-config-insecure-ssl

optional

One of

string

number

Determines whether the SSL certificate of the host for url will be verified when delivering payloads. Supported values include 0 (verification is performed) and 1 (verification is not performed). The default is 0. We strongly recommend not setting this to 1 as you are subject to man-in-the-middle and other attacks.

Example:

"0"

secret

string

optional

If provided, the secret will be used as the key to generate the HMAC hex digest value for delivery signature headers.

Example:

"********"

url

string <uri>

optional

The URL to which the payloads will be delivered.

Example:

https://example.com/webhook

Examples

Responses

🟢200Response

application/json

Body

Configuration object of the webhook

content_type

string

optional

The media type used to serialize the payloads. Supported values include json and form. The default is form.

Example:

"json"

insecure_ssl

webhook-config-insecure-ssl

optional

One of

string

number

Example:

"0"

secret

string

optional

If provided, the secret will be used as the key to generate the HMAC hex digest value for delivery signature headers.

Example:

"********"

url

string <uri>

optional

The URL to which the payloads will be delivered.

Example:

https://example.com/webhook

Modified at 2023-08-15 02:59:28

Get a webhook configuration for an organization

List deliveries for an organization webhook