sinch-api-webhooks-update

Update an existing Sinch Conversation API webhook's target URL, triggers, or secret.

6|2|Updated Dec 11, 2025
One-click install
npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-webhooks-update-sinch
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sinch-api-webhooks-update
Source: https://github.com/sinch/sinch-plugins/tree/main/plugins/sinch-antigravity-plugin/skills/sinch-api-webhooks-update
Command: npx skills add https://github.com/sinch/sinch-plugins --skill sinch-api-webhooks-update-sinch

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Modifying an existing Sinch Conversation API webhook normally requires manually crafting authenticated PATCH requests against the regional API endpoint. This Skill updates a webhook's target URL, triggers, or secret directly from the conversation, handling OAuth2 authentication and configuration retrieval automatically. ## Core Features & Use Cases - Partial Updates: Change only the fields you specify (target, triggers, or secret) while preserving all other existing webhook settings. - Interactive Mode: Prompts for the webhook ID and new values when no arguments are provided. - Flexible Configuration: Reads credentials from the Sinch MCP server when available, falling back to environment variables. - Use Case: Your backend endpoint migrated to a new domain. Run the update command with the webhook ID and new HTTPS target URL to redirect event delivery without recreating the webhook. ## Quick Start Ask the assistant to update webhook 01E9WEBHOOK123 with the new target URL https://newurl.com/webhook using the Sinch API.

Frequently Asked Questions about sinch-api-webhooks-update

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I update a Sinch Conversation API webhook?

Provide the webhook ID with --id plus at least one field to change: --target for the URL, --triggers for the event list, or --secret for the token. The Skill sends an authenticated PATCH request to the regional Conversation API endpoint.

How do I change a webhook target URL in Sinch?

Run the update command with the webhook ID and the new HTTPS target, for example --id=01E9WEBHOOK123 --target=https://newurl.com/webhook. The target must be publicly accessible and use HTTPS.

What credentials are required to update Sinch webhooks?

The Skill uses the Sinch MCP configuration when available, otherwise it reads CONVERSATION_PROJECT_ID, CONVERSATION_REGION, CONVERSATION_KEY_ID, and CONVERSATION_KEY_SECRET environment variables. OAuth2 authentication with the key ID and secret generates the access token.

Does updating webhook triggers replace the existing trigger list?

Yes, trigger updates are not incremental. You must provide the complete comma-separated list of triggers, such as MESSAGE_DELIVERY,MESSAGE_INBOUND,CONVERSATION_START, which replaces the previous configuration.

What happens to the old secret when I rotate a webhook secret?

Changing the secret invalidates the old one immediately. Any signature validation using the previous secret will fail, so update your receiving endpoint's verification logic at the same time.