Set webhook state

set_webhook_state Activate or disable one endpoint. Disabling stops delivery and loses nothing: undelivered events stay in the feed and can be read with a cursor. Re-enabling clears the failure count.

Hosted MCP registration verified. These schemas describe the development contract; confirm supported inputs with tools/list. Generic CLI/HTTP calls require a matching development server. Configure LINKTRAIL_API_URL; production does not expose these command routes.

Access	Behavior
`watches:write`	Writes or admits work; can change or remove existing state

Reading saved data does not start a verification job. Mutations can change saved records or access; the effects below apply.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "set_webhook_state",
    "arguments": {
      "endpointId": "endpoint_example",
      "state": "active"
    }
  }
}

linktrail call set_webhook_state --args '{"endpointId":"endpoint_example","state":"active"}'

curl "$LINKTRAIL_API_URL/v1/commands/set_webhook_state" \
  -H "Authorization: Bearer $LINKTRAIL_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{"endpointId":"endpoint_example","state":"active"}'

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

{
  "id": "endpoint_example",
  "state": "active"
}

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Field	Type	Presence	Meaning and constraints
`endpointId`	string	Required	Identifier of the endpoint returned by its create or list operation. minLength: 1; maxLength: 200
`state`	string	Required	Requested resource state or saved-observation filter, as enumerated here. values: “active”, “disabled”

Validation and omitted values

Reactivation clears the failure count. Disabling stops delivery; recover undelivered retained history through the corresponding event feeds.

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.

Field	Type	Presence	Meaning and constraints
`id`	string	Required	Resource identifier returned by the operation.
`state`	string	Required	Saved lifecycle or evidence state, as enumerated for this record. values: “active”, “disabled”

Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Method and route	Success	Details
`PATCH /v1/webhooks/{endpointId}`	200	Remaining arguments go in a JSON object body.

Continue

list_webhooks · list_link_events · list_target_events Follow the related workflow, inspect capability status, or return to the command index.

Overview

Cloud operations

Repository tools

HTTP and events

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Input fields

​Validation and omitted values

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Input fields

Validation and omitted values

Output fields

Errors and retries

HTTP resource routes

Continue