create_webhook Early access Write
This tool is in early access. It is available at
https://mcp.tuyo.com/mcp-early-access to accounts with Pods early access. See Early access.Description
The model reads this text to decide when and how to call the tool.Create a plain webhook to send selected Tuyo events to the user’s public HTTPS receiver. Choose events and filters from list_webhook_events. Transaction events follow the main account only unless accountIds selects pods or the main account explicitly. Make sure the receiver can get its signing secret privately before creating. Callback verification requires a supplied secret. Keep secrets out of chat. Separate calls can create duplicate deliveries. After an uncertain outcome, check list_webhooks first. A host watching events in a conversation uses native MCP Events.
Input
Receiver signing secret, whsec_ followed by 24 to 64 base64-encoded bytes. Supply an existing key only through a client integration that keeps it out of chat and model context. Never ask the user to paste it into chat. With verification off, omit this field only if the receiver operator can retrieve the generated key privately from structuredContent. Otherwise defer creation.
Optional headers sent with every delivery and with the verifyCallback challenge, such as {“Authorization”: “Bearer <token>”} when the receiver requires one. Up to 10. Values are write-only: list_webhooks shows only the names.
Set true only when the receiver answers the Tuyo signed challenge, to confirm the URL before creating the webhook. It needs secret. Omit it otherwise.
Output
The structured result is{ data, meta }. meta has the requestId and the asOf time. These are the fields of data. An error returns { error, meta }; see Errors.