sinch-api-webhooks-delete

Delete Webhook

Delete a webhook from your Sinch Conversation app. This will stop all event notifications to the webhook's target URL.

IMPORTANT: Execute this command directly. Do NOT generate script files. Do NOT create Python/JavaScript files. Perform the API call immediately using the instructions below.

Input

• --id / -i: Webhook ID to delete (required)
• --force / -f: Skip confirmation prompt (optional)

Arguments: $ARGUMENTS

Instructions

Execute these steps directly - do not write code or scripts:

1. Check if $ARGUMENTS is empty or only contains the command name:

   • If empty or no meaningful arguments provided, enter interactive mode:
     • First, list all webhooks to help user choose
     • Ask: "🆔 Which webhook ID do you want to delete?"
     • Use the provided answer as the webhook_id for the following steps
   • If arguments are provided, proceed directly to step 1

2. Parse and validate arguments from $ARGUMENTS or interactive input:

   • Validate that --id is provided and non-empty
   • Check if --force flag is present

3. Try to call mcp__sinch__sinch-mcp-configuration to get the current configuration.

4. If MCP is NOT available, retrieve configuration from environment variables:

   • CONVERSATION_PROJECT_ID
   • CONVERSATION_REGION
   • CONVERSATION_KEY_ID
   • CONVERSATION_KEY_SECRET
   • If any are missing, report: "Sinch API is not configured. Please set the required environment variables."

5. Verify the webhook exists:

   • Retrieve the webhook details
   • If not found, report: "Webhook with ID '{webhook_id}' not found"
   • Display the webhook configuration to the user

6. Request confirmation unless --force is specified:

   • Display: "⚠️ Are you sure you want to delete this webhook?"
   • Show webhook details: ID, Target URL, Triggers
   • Ask: "Type 'yes' to confirm deletion:"
   • If user doesn't confirm, abort with message: "Webhook deletion cancelled"

7. Delete the webhook using the Sinch Conversation API:

   • Endpoint: DELETE https://{region}.conversation.api.sinch.com/v1/projects/{projectId}/webhooks/{webhookId}
   • Use OAuth2 authentication with key ID and secret to generate access token