---
title: "Repoint a webhook endpoint"
method: PATCH
path: "/api/v1/webhook-endpoints/{endpointId}"
tags: ["Webhook endpoints"]
---

# Repoint a webhook endpoint

`PATCH /api/v1/webhook-endpoints/{endpointId}`

## Request

- Base URL: `https://app.dodomain.io`
- URL: `https://app.dodomain.io/api/v1/webhook-endpoints/{endpointId}`
- Auth: HTTP bearer

Points an existing endpoint at a new URL. PATCH rather than PUT because `url` is the only mutable field, so the body is a partial by construction. The signing secret is deliberately UNTOUCHED — moving hosts must not force a receiver to re-key; rotating is the explicit sibling call. Same URL policy and same duplicate rule as create; the plan cap is NOT re-checked, because an update never grows the set and an app already over a lowered cap must still be able to fix a wrong URL. A URL that actually CHANGES also resumes an auto-paused endpoint (`pausedAt` back to null) and restarts its 7-day clock — a new address is the usual fix for a dead one. An unknown id and another app's id both answer 404.

## Path parameters

- `endpointId` string, required

## Headers

- `DoDomain-Team` string

## Request body

- WebhookEndpointInput
  - `url` string, required

## Response `200`

Success.

- WebhookEndpointSummary
  - `appId` string, required
  - `createdAt` string, date-time, required
  - `id` string, required
  - `pausedAt` string, date-time, nullable, required
  - `url` string, required

## Other responses

- `400`: `400 invalid_request` — The request body or query failed schema validation, or a documented capability rule rejected it. `details` carries the field-level report when the failure came from schema validation.
- `401`: `401 unauthorized` — No `Authorization: Bearer` header, or the credential is malformed, unknown, or (for OAuth tokens) fails verification.
- `403`: `403 forbidden` — The OAuth access token was not granted the scope this operation requires. `details.code` is `SCOPE_MISSING` and `details.requiredScope` names the scope. Secret keys (`dd_sk_`) carry no scopes and never see this for a missing scope. The one-click start routes also answer it for a session created without one-click (a Free-plan team's session): no `details`, and the end user falls back to the manual records.
- `404`: `404 not_found` — The addressed resource does not exist, or the caller does not own it — the two collapse to one status on purpose, so an id cannot be enumerated by a caller who does not own it.
- `429`: `429 rate_limited` — Rate limited. `Retry-After` (seconds) is set and `details.retryAfterSeconds` repeats it. Branch on `details.reason`: `request_rate` means the caller is calling too fast (`details.limit` carries the cap), `recently_checked` means this one connection was DNS-checked inside its cooldown.
- `500`: `500 internal` — An unhandled server-side failure. Reported to our error tracker; safe to retry.

---

[API](https://skmtc.dev/dodomain/apis/dodomain-api.md) · [All operations](https://skmtc.dev/dodomain/apis/dodomain-api/llms.txt) · [OpenAPI document](https://skmtc.dev/dodomain/apis/dodomain-api/revisions/44cfb944de58?raw)