Show a webhook subscription
AI agents: read /llms.txt; add .md to any page URL. This page as Markdown: /reference/webhook-subscriptions/v1-webhook-subscription-show.md. Index of every page and the rules for every call: /llms.txt. Guides and concepts in one file: /llms-full.txt. OpenAPI: /openapi.json.
GET/
Returns one webhook subscription with its status and disable_reason, and its signing secret for the team owner and members with Manage Settings.
Check status when deliveries stop: a subscription can be turned off by hand or by YoPrint after repeated failures (disable_reason auto_disable_too_many_errors).
Path parameters
Your team slug, shown as Team ID next to your API key in Profile.
- Example
your-team
- Example
The webhook subscription's
id: a hash id from an earlier answer. Only hash ids work here; anything else answers 404page_not_found.- Example
V4keXwwxMQyXw7
- Example
Request body
This operation takes no request body.
Response
200Successful response.
Child fields (10)
auto_disable_too_many_errorswhen YoPrint turned the subscription off because its deliveries kept failing. Otherwise null. Settingstatusback toactivedoes not clear it.Subscribed event names, or
allfor every event.The subscription id.
The secret used to sign event payloads:
whsec_followed by 32 letters and digits. Use it to verify incoming messages. YoPrint creates it when the subscription is created and never changes it. Keep it private. Only the team owner and members whose permission group has Manage Settings can see it; for every other member it is null. It is also null for AI apps reading through YoPrint's MCP server.The
sourcesent when the subscription was created: the web app sendsyoprint, YoPrint's Zapier app sendszapier.Only
activesubscriptions receive events.- One of:
"active","disabled"
- One of:
The destination URL where YoPrint delivers events. On this API, this is the full URL. AI apps reading subscriptions through YoPrint's MCP server see only the origin (scheme and host, such as
https://example.com) to protect webhook secrets.
Errors
401The API key is missing or wrong (
unauthenticated).- When
- The API key is missing or wrong.
- Fix
- Send your personal API key as
Authorization: Bearer YOUR_API_KEY.
403You are not allowed to do this.
api_access_not_in_plan: your team's plan doesn't include API access (Pro and above, with an active subscription or trial), so every request answers this until the team upgrades. When your role lacks the permission the operation needs, the body is only{"message": "Insufficient Permission"}. Other refusals use the error envelope, withunauthorizedoruser_is_not_authorized.404Not found.
page_not_found: the team slug is unknown, you are not a member of the team, or an id in the path is not one of this team's.code: null, with a message that starts "No query results for": there is no record with that id.- When
- No webhook subscription with that id on this team (
error.codeis null anderror.messagestarts "No query results"), the id is not one of this team's hash ids, or you are not a member of the team (bothpage_not_found). - Fix
- Use an
idfrom the list operation and check the team slug.
Notes
- The status filters (
config) are not returned.
Related
- PATCHTouch a webhook subscription
/v1/ api/ store/ {team_slug}/ setting/ webhook_subscription/ {hash_id} - GETList deliveries for a webhook subscription
/v1/ api/ store/ {team_slug}/ setting/ webhook_subscription/ {id}/ log
