Skip to main content
Slipway delivers deployment notifications to user-configured channels via HTTPS POST. Discord and Slack receive platform-native payloads; generic webhook channels receive the schema below.

Request

  • Method: POST
  • Content-Type: application/json
  • User-Agent: slipway-notifier/1
  • X-Slipway-Signature: sha256=<hex> — present only when the channel has a signing secret configured (see HMAC signing).
  • Timeout: 10 seconds. Non-2xx responses and timeouts are recorded as notification_failed events and are not retried — design your receiver to be idempotent.

Body

Field reference

The updated event uses the same shape as healthy — there is no extra “previous deployment” reference. If you need that, look up the repo’s deployments via the API and find the most recent superseded row for the same pr_number.

HMAC signing

When the channel has a signing secret, slipway includes:
The digest is computed exactly as:
…over the raw bytes of the request body, not a re-serialised version. Verify in constant time before trusting the payload. Example in Go:
The signing scheme intentionally mirrors slipway’s inbound GitHub webhook verifier, so any code you already have for verifying GitHub webhooks will need only a header-name change.

Delivery failures

If your endpoint returns a non-2xx status or doesn’t respond within 10 seconds, slipway writes a notification_failed event to the deployment with data.channel_id. Deliveries aren’t retried — keep your receiver idempotent and use the deployment timeline to spot delivery problems.