Source type
Bitbucket Source Configuration
Bitbucket sources receive repository, pull request, branch, tag, and build status webhooks with HMAC verification.
Bitbucket configuration
Create a Bitbucket source, keep POST and PUT and PATCH and DELETE enabled, and provide the configured Webhook Signing Secret values for provider signature. FastHook uses these settings to validate each Bitbucket delivery before it enters the routing workflow.
Source TypeBITBUCKET
Allowed methodsPOST, PUT, PATCH, DELETE
AuthenticationProvider signature
Credential fieldsWebhook Signing Secret
{
"type": "BITBUCKET",
"config": {
"auth_type": "PROVIDER_SIGNATURE",
"auth": {
"provider": "BITBUCKET",
"webhook_signing_secret": "provider-secret"
},
"allowed_http_methods": ["POST","PUT","PATCH","DELETE"]
}
}Bitbucket request contract
FastHook computes sha256= HMAC-SHA256 over the raw body and compares it with x-hub-signature.
Bitbucket headers
Preserve x-hub-signature, x-event-key when sending Bitbucket test deliveries. FastHook evaluates this request context before accepting the payload, so missing or modified values remain visible as rejected requests instead of routed events.
x-hub-signaturesha256= HMAC-SHA256 signature over the raw body.
x-event-keyBitbucket event key, useful for routing.
Bitbucket setup
- Create a Bitbucket Cloud webhook using the FastHook Source URL.
- Paste the webhook secret into FastHook.
- Route by x-event-key or repository fields.