For AI agents: a documentation index is available at the root level at /llms.txt and /llms-full.txt. Append /llms.txt to any URL for a page-level index, or .md for the markdown version of any page.
13.5kProductPricingSign inStart free trialBook a demo
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
DocsAPIsSDKsEnterprise EdgeGuidesAcademyRelease notes
    • Home
  • Get started
    • Quickstart
    • Introduction to feature flags
    • Unleash architecture overview
  • Core concepts
    • Overview
    • Import and export
      • Unleash hosting options
        • Integrations overview
        • Datadog
        • Slack
        • Microsoft Teams
        • Terraform
        • Webhook
      • Developer Toolbar

Unleash reduces the risk of releasing new features, drives innovation by streamlining the software release process, and increases revenue by optimizing end-user experience. While we serve the needs of the world's largest, most security-conscious organizations, we are also rated the “Easiest Feature Management system to use” by G2.

GitHubGitHubLinkedInLinkedInX (Twitter)X (Twitter)SlackSlackStack OverflowStack OverflowYouTubeYouTube

Server SDKs

  • Node.js
  • Java
  • Go
  • Rust
  • Ruby
  • Python
  • .NET
  • PHP
  • All SDKs

Frontend SDKs

  • JavaScript
  • React
  • Next.js
  • Vue
  • iOS
  • Android
  • Flutter

Feature Flag use cases

  • Secure, scalable feature flags
  • Rollbacks
  • FedRAMP, SOC2, ISO2700 compliance
  • Progressive or gradual rollouts
  • Trunk-based development
  • Software kill switches
  • A/B testing
  • Feature management
  • Canary releases

Product

  • Quickstart
  • Unleash architecture
  • Pricing
  • Product vision
  • Open live demo
  • Open source
  • Enterprise feature management platform
  • Unleash vs LaunchDarkly

Support

  • Help center
  • Status
  • Changelog
Made in a cosy atmosphere in the Nordic countries.Copyright © 2026 Unleash
LogoLogo
13.5kProductPricingSign inStart free trialBook a demo
On this page
  • Configuration
Integrate and deployIntegrations

Webhook

||View as Markdown|
Was this page helpful?

Last updated May 11, 2026

Previous

Unleash MCP Server

Next
Built with
v3.11

The Webhook Integration introduces a generic way to post messages from Unleash to third party services. Unleash allows you to define a webhook which listens for changes in Unleash and posts them to third party services.

The webhook will perform a single retry if the HTTP POST call fails (either a 50x or network error). Duplicate events may happen, and you should never assume events always comes in order.

Configuration

Events

You can choose to trigger updates for the following events (we might add more event types in the future):

  • feature-created
  • feature-metadata-updated
  • feature-project-change
  • feature-archived
  • feature-revived
  • feature-strategy-update
  • feature-strategy-add
  • feature-strategy-remove
  • feature-stale-on
  • feature-stale-off
  • feature-completed
  • feature-environment-enabled
  • feature-environment-disabled
  • feature-variants-updated
  • feature-tagged
  • feature-untagged
  • change-request-created
  • change-request-discarded
  • change-added
  • change-discarded
  • change-request-approved
  • change-request-approval-added
  • change-request-cancelled
  • change-request-sent-to-review
  • change-request-applied
  • change-request-scheduled
  • change-request-scheduled-application-success
  • change-request-scheduled-application-failure
  • change-request-schedule-suspended
  • feature-potentially-stale-on
  • feature-updated (deprecated in v4.3)

Parameters

Unleash Webhook integration takes the following parameters.

Webhook URL This is the only required property. If you are using a Slack Application you must also make sure your application is allowed to post the channel you want to post to.

Content-Type Used to set the content-type header used when unleash performs an HTTP POST to the defined endpoint.

Body template Used to override the body template used by Unleash when performing the HTTP POST. You may format you message using a Mustache template. You will have the Unleash event format available in the rendering context:

GET
/api/admin/events
1curl https://app.unleash-instance.example.com/api/admin/events \
2 -H "Authorization: <apiKey>"
Try it

Example:

1{
2 "event": "{{event.type}}",
3 "createdBy": "{{event.createdBy}}",
4 "featureToggle": "{{event.data.name}}",
5 "timestamp": "{{event.data.createdAt}}"
6}

If you don’t specify anything Unleash will use the Unleash event format:

GET
/api/admin/events
1curl https://app.unleash-instance.example.com/api/admin/events \
2 -H "Authorization: <apiKey>"
Try it

Custom SSL certificates

If your webhook endpoint uses a custom SSL certificate, you will need to start Unleash with the NODE_EXTRA_CA_CERTS environment variable set. It needs to point to your custom certificate file in pem format.

For more information, see the official Node.js documentation on setting extra certificate files.