Update a webhook endpoint · SocialTap API reference

Changes the URL, events, description or status; absent fields keep their value. Setting status to enabled re-enables an endpoint SocialTap disabled (see disabled_reason). Free.

Auth: an API key with the admin scope, or the dashboard session.

Test mode: A test key manages the account's test webhook endpoints, separate from live ones; they receive test events only (a test job's job.* events and webhook.test), signed and retried like live ones.

Example

cURL

curl -X PATCH 'https://staging.socialtap.dev/v1/webhook_endpoints/<id>' \
  -H "x-api-key: $SOCIALTAP_API_KEY" \
  -H "content-type: application/json" \
  -d '{
  "description": "string",
  "events": [
    "string"
  ],
  "status": "enabled",
  "url": "string"
}'

Authorizations

x-api-keystringheaderrequired

Your API key, with the admin scope. Authentication

Path parameters

Name	Type	Description	Example
`id` required	`string`	Webhook endpoint ID (we_…).	—

idstringrequired

Webhook endpoint ID (we_…).

Body

application/json

JSON. Fields marked nullable may be null; optional ones may be left out.

Field	Type	Description
`description?`	`string` or `null`
`events?`	`string[]` or `null`
`status?`	`string` or `null`	One of `enabled`, `disabled`
`url?`	`string` or `null`

description?stringnullable

events?string[]nullable

status?stringnullable

One ofenableddisabled

url?stringnullable

Response

application/json

200

Update a webhook endpoint

Field	Type	Description
`data`	`object`
`data.created_at`	`string` (date-time)
`data.description`	`string` or `null`
`data.disabled_reason`	`string` or `null`	Why it is disabled: gone (it answered 410), failing (deliveries failed for 5 days), user. Null while enabled. One of `gone`, `failing`, `user`
`data.events`	`string[]`	Event types it receives: types, prefix wildcards (job.) or for all.
`data.id`	`string`	we_…
`data.object`	`string`	Always webhook_endpoint. One of `webhook_endpoint`
`data.previous_secret_expires_at`	`string` (date-time) or `null`	Until then the previous secret signs too; null when none.
`data.secret?`	`string` or `null`	The signing secret (whsec_…): only in the create and rotate_secret answers. Store it.
`data.status`	`string`	One of `enabled`, `disabled`
`data.updated_at`	`string` (date-time)
`data.url`	`string`	https URL deliveries are POSTed to.
`meta`	`object`	The shared route meta (see the API reference introduction).

dataobject

Show 11 child fields

created_atstring date-time

descriptionstringnullable

disabled_reasonstringnullable

Why it is disabled: gone (it answered 410), failing (deliveries failed for 5 days), user. Null while enabled.

One ofgonefailinguser

eventsstring[]

Event types it receives: types, prefix wildcards (job.*) or * for all.

idstring

we_…

objectstring

Always webhook_endpoint.

One ofwebhook_endpoint

previous_secret_expires_atstring date-timenullable

Until then the previous secret signs too; null when none.

secret?stringnullable

The signing secret (whsec_…): only in the create and rotate_secret answers. Store it.

statusstring

One ofenableddisabled

updated_atstring date-time

urlstring

https URL deliveries are POSTed to.

metaobject

The shared route meta (see the API reference introduction).

400

400 Bad Request.

Code	HTTP	Retry	Meaning	What to do
`invalid_input`	400	No	The request parameters are missing or malformed, or the URL is not a supported link for this endpoint.	Fix the parameter named in param (the message says how); for a link of the wrong kind, call the endpoint the message names.

invalid_inputNo retry

The request parameters are missing or malformed, or the URL is not a supported link for this endpoint.

Fix the parameter named in param (the message says how); for a link of the wrong kind, call the endpoint the message names.

401

401 Unauthorized.

Code	HTTP	Retry	Meaning	What to do
`unauthorized`	401	No	The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).	Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

unauthorizedNo retry

The x-api-key header is missing, unknown or revoked (or, on the dashboard's routes, the session cookie is missing or expired).

Send a valid API key in the x-api-key header; without one, get a key at details.signup_url (AI agents: POST details.agent_signup_url).

403

403 Forbidden.

Code	HTTP	Retry	Meaning	What to do
`forbidden`	403	No	The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include. A running job stops the same way when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item (a private item is private_or_unavailable, also 403): branch on the code.	Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope), have the owner confirm the emailed link, create a new key, or call from an allowed IP.

forbiddenNo retry

The API key is valid but may not make this request: its account is suspended, its scopes do not include the route, it is waiting for its owner's email confirmation, it is past its expiry, or the request came from an IP its allowlist does not include. A running job stops the same way when its account is suspended or the key that created it is revoked or expires. It is about the key, never the item (a private item is private_or_unavailable, also 403): branch on the code.

Do what details.reason says: if suspended, contact support; otherwise use a key whose scopes cover the route (details.required_scope), have the owner confirm the emailed link, create a new key, or call from an allowed IP.

404

404 Not Found.

Code	HTTP	Retry	Meaning	What to do
`not_found`	404	No	The item does not exist or was deleted.	Check the URL or ID; do not retry.

not_foundNo retry

The item does not exist or was deleted.

Check the URL or ID; do not retry.

429

429 Too Many Requests.

Code	HTTP	Retry	Meaning	What to do
`rate_limited`	429	Yes, later	The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.	Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

rate_limitedYes, later

The account exceeded its runaway-protection ceiling: plans do not limit request rate, but a high per-account safety ceiling stops broken client loops. Support raises it on request. Without an API key (signup, the MCP server's tool listing and find_endpoint), requests are limited per IP address instead.

Wait for the number of seconds in the retry-after header, then retry; ask support to raise the ceiling if your sustained traffic needs more (calls without an API key: use one).

Test mode

A test key manages the account's test webhook endpoints, separate from live ones; they receive test events only (a test job's job.* events and webhook.test), signed and retried like live ones.

operationId webhook_endpoints.update