Terraform

The Webhookr Terraform provider lets you manage Webhookr resources as code instead of clicking through the dashboard. It supports projects, endpoints, and destinations.

Why use Terraform with Webhookr

• Reproducible setup — define endpoints and destinations once and apply them across environments.
• Reviewable changes — webhook routing lives in version control and goes through code review.
• No manual drift — Terraform reconciles the real state with your configuration.
• Automation-friendly — provision Webhookr from CI/CD pipelines with an API token.

What you can manage

Resource	Manages
webhookr_project	A project.
webhookr_endpoint	An endpoint within a project.
webhookr_destination	A delivery target on an endpoint.

At a glance

terraform {
  required_providers {
    webhookr = {
      source = "forgers-tech/webhookr"
    }
  }
}

provider "webhookr" {
  api_url = "https://api.webhookr.tech"
  # api_token supplied via WEBHOOKR_API_TOKEN
}

resource "webhookr_project" "payments" {
  name = "payments-prod"
}

resource "webhookr_endpoint" "stripe" {
  project_id = webhookr_project.payments.id
  name       = "Stripe events"
}

resource "webhookr_destination" "orders" {
  project_id  = webhookr_project.payments.id
  endpoint_id = webhookr_endpoint.stripe.id
  name        = "Order service"
  url         = "https://orders.internal.example.com/webhooks/stripe"
}

:::info Provider availability The provider's source address is forgers-tech/webhookr. If it isn't yet published to the public Terraform Registry for your setup, install it from your internal registry or as a local provider using the same source address. :::

Next

• Authentication — API token vs. Firebase service account.
• Resources — every argument and attribute.
• Complete example — a minimal end-to-end configuration.
• Best practices — tokens, secrets, and rotation.