One webhook endpoint (never its secret). Free.
Auth: an API key with the account:read scope, or the dashboard session.
Example
curl 'https://socialtap.dev/v1/webhook_endpoints/<id>' \
-H "x-api-key: $SOCIALTAP_API_KEY"Webhook endpoint ID (we_…).
Response
200
Get a webhook endpoint
dataobjectShowHide 12 child fields
created_atstring date-timecreated_by_userstringnullableThe person (GET /v1/members user_id) who created this endpoint in the dashboard, or whose API key created it. They may have left the account since. Null when no person did, or it is from before this was recorded.
descriptionstringnullabledisabled_reasonstringnullableWhy 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.
idstringwe_…
objectstringAlways webhook_endpoint.
One ofwebhook_endpoint
previous_secret_expires_atstring date-timenullableUntil then the previous secret signs too; null when none.
secret?stringnullableThe signing secret (whsec_…): only in the create and rotate_secret answers. Store it.
statusstringOne ofenableddisabled
updated_atstring date-timeurlstringhttps URL deliveries are POSTed to. A key an agent collected from an approval reads only its host: https://host/.
metaobjectThe shared route meta (see the API reference introduction).
400
400 Bad Request.
invalid_inputNo retryA parameter is missing or malformed, or the link is not one this endpoint takes.
Fix the parameter named in param as the message says. For a link of the wrong kind, call an endpoint listed in details.endpoints, when there is one.
401
401 Unauthorized.
unauthorizedNo retryThe x-api-key header is missing, or its key is unknown or revoked. On the dashboard's routes: the session cookie is missing or expired.
Send a valid API key in the x-api-key header. No key yet? A person gets one at details.signup_url; an AI agent follows details.agent_auth_url.
403
403 Forbidden.
forbiddenNo retryThe API key is valid but may not make this request, and details.reason says why: the account is suspended, the key lacks the route's scope, waits for its owner to confirm it by email, has expired, or was used from an IP outside its allowlist, or a rotated key's previous secret was used for a call that needs the admin scope. A running job stops with it too 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, so branch on the code.
Act on details.reason. suspended: contact support. scope: use a key with details.required_scope. previous_secret: use the new secret. key_pending: have the owner open the emailed link. key_expired or key_revoked: create a new key. ip_not_allowed: call from an allowed IP.
404
404 Not Found.
not_foundNo retryThe item does not exist or was deleted. On GET /v1/requests/{id}/response: the response was not kept (details.reason says why).
Check the link or ID. Do not retry.
429
429 Too Many Requests.
rate_limitedYes, laterThe account passed its runaway-protection ceiling: a high per-account limit that stops a broken client loop (plans have no rate limit). Requests without an API key (signup, the MCP server's tool listing and find_endpoint) are limited per IP address instead. It also stops an account whose failed requests in the last hour cost far more than its successful ones paid for: failures are free within a limit (the message says so), and successes raise it.
Wait the seconds in the retry-after header, then retry. If your steady traffic needs more, ask support to raise the ceiling; without an API key, send one.
operationId webhook_endpoints.get