Skip to main content
Webhooks let you receive real-time HTTP notifications when events occur in your project. DevTune will POST a JSON payload to your configured URL whenever a subscribed event fires.

Event Types

action.* events track the action entity lifecycle. action.recommendation.* events track the recommendation surface. Recommendation update events are intentionally quiet: they do not fire for recommendation reorder, acceptance, small citation drift, evidence reorder, wording-only changes, or brief absence alone. action.status is suggested, accepted, live or archived, the same values the actions API returns. action.blocked is true on accepted work your team has marked blocked. A suggestion DevTune withdraws before anyone acts on it sends no further events.

Managing Webhooks via the Dashboard

You can create and manage webhooks directly from your account settings in the DevTune dashboard.
  1. Navigate to your team account
  2. Open Webhooks in the account sidebar
  3. Click Create Webhook
  4. Fill in the form:
    • Endpoint URL — The HTTPS URL that will receive webhook POST requests
    • Project — Select which project’s events should trigger the webhook
    • Events — Check one or more event types to subscribe to
  5. Click Create Webhook
  6. Copy the signing secret shown in the dialog — this is the only time it will be displayed
  7. If you ever need a new secret, click the rotate icon next to the webhook — this generates a new secret and invalidates the old one immediately
You can view all your webhooks in the table, and delete any active webhook using the trash icon. Use the “Hide inactive” toggle to filter out previously deleted webhooks.
Note: The Webhooks page requires the Plus plan or above (API Access entitlement). You must also have the settings.manage permission on the team account.

Managing Webhooks via the API

Scoped API keys must include:
  • webhooks.read to list webhook subscriptions
  • webhooks.write to create, delete, or rotate webhook secrets

Create a Webhook

Request Body

Response (201)

The secret is only returned when creating the webhook. Store it securely for signature verification.

List Webhooks

Returns all active webhook subscriptions for the project.

Response (200)

Delete a Webhook

Deactivates the webhook subscription.

Response (200)

Returns 404 if the webhook ID does not exist or belongs to a different project.

Rotate Webhook Secret

Generates a new HMAC-SHA256 signing secret for the webhook. The old secret is invalidated immediately — any deliveries signed with the old secret will no longer verify. No request body is required.

Response (200)

Returns 404 if the webhook does not exist, belongs to a different project, or is inactive.

Webhook Payload Format

When an event fires, DevTune sends a POST request with this body:

visibility.changed payload

previousMetrics is null when there is no prior data (e.g., the first run for a project).

action.created payload

action.updated payload

action.recommendation.created payload

When a live recommendation is ranked on the opportunity contract, recommendationContext.opportunity carries the same percentile, percentilePoolSize, components, estimated, family and measuredFacts fields the actions API returns for that action. action.portfolioRank is its persisted position in the project queue (ascending, nulls last). Legacy scalar scores are not included. Citation-defence recommendations additionally carry the published window date, current and prior citation counts, and probe-day coverage in measurements. Events for adopted actions omit it, because only live recommendations are re-ranked each refresh.

action.recommendation.updated payload

action.recommendation.updated uses the same payload shape as action.recommendation.created, with recommendationContext.changeReasons explaining why review is recommended.
To fetch full context after either event, use:
  • GET /api/v2/projects/{projectId}/actions/list?detailLevel=context
  • GET /api/v2/projects/{projectId}/actions/{actionId}/brief
  • GET /api/v2/projects/{projectId}/actions/{actionId}/events for who changed an action and what they changed
  • MCP devtune_get_actions with detailLevel: "context"
  • MCP devtune_get_action_brief
  • MCP devtune_get_action_events

Headers

Verifying Signatures

Every webhook delivery includes an X-DevTune-Signature header containing an HMAC-SHA256 hex digest computed with your webhook secret.

Node.js Example

Important: Use the raw request body (before JSON parsing) for signature verification. In Express, use express.raw({ type: 'application/json' }) on your webhook route to get the raw buffer.

Python Example

Retry Policy

Failed deliveries (non-2xx responses or timeouts) are retried up to 3 times with exponential backoff. Each attempt is logged in the delivery log visible in the DevTune dashboard.

Use Cases

  • Slack notifications when a tracking run finishes
  • CI/CD triggers to re-run checks when visibility changes
  • Data pipelines that sync DevTune data to your warehouse on each update
  • GTM automation that feeds generated actions into triage systems or agentic workflows
percentilePoolSize counts rankable candidates in the full signal family before selection or pagination. A size of one means the only ranked opportunity of this type, not Top 1%. Older records omit this field; do not infer singleton status from a percentile of 100 or the number of returned actions.