GitHub App events
Where GitHub sends every event of the CoderHelm GitHub App. Installing the app sets this up; you only call it yourself when you self-host. Each request is signed with the app's webhook secret in X-Hub-Signature-256 (sha256= and the hex HMAC-SHA256 of the raw body), compared in constant time. The event type comes from X-GitHub-Event and the body must name an installation. Events CoderHelm doesn't act on, and events from an installation not linked to a team, are accepted with 200 and ignored.
github_signatureX-Hub-Signature-256<token>sha256= and the hex HMAC-SHA256 of the raw body, keyed with the GitHub App's webhook secret.
X-GitHub-Event*stringThe event type, such as issues, pull_request or push.
X-GitHub-Delivery?|GitHub's id for this delivery.
The event payload, as GitHub defines it for each event type. It must include installation.id.
application/json- body
Accepted.
curl -X POST 'https://api.coderhelm.com/webhooks/github' \ -H 'X-GitHub-Event: issues' \ -H 'Content-Type: application/json' \ -d '{}'AWS SNS alerts POST
Subscribe CoderHelm to an SNS topic with an HTTPS subscription to this address and add the topic under Alert routes in the dashboard. Every message's SNS signature is checked (signature versions 1 and 2) and the signing certificate must come from SNS. The subscription is confirmed automatically once the topic has an enabled route; messages from topics without one are accepted and ignored. A message that matches one of the route's rules becomes a run that opens a pull request.
Jira webhook POST
For a plain Jira webhook, when the CoderHelm Jira app can't be installed. The URL holds a token generated for your team on the Jira page of the dashboard. If you also generated a secret there, every request must carry `X-Hub-Signature`: `sha256=` and the hex HMAC-SHA256 of the raw body, keyed with that secret. Jira Cloud signs webhooks this way when you set the secret on the webhook; a Jira automation can send the header itself.