# Sinch API Webhooks Triggers

> Show available webhook trigger types for Sinch Conversation API

- Skill: `sinch/sinch-api-webhooks-triggers` (Agent Skill)
- Install (CLI): `npx skillmds@latest add sinch/sinch-api-webhooks-triggers`
- Raw SKILL.md: https://api.skillmd.com/api/skills/sinch/sinch-api-webhooks-triggers/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Integrations & APIs
- Author: sinch (https://skillmd.com/u/sinch)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/sinch/sinch-api-webhooks-triggers

---


# Webhook Triggers Reference

Display all available webhook trigger types for the Sinch Conversation API. Use this as a reference when creating or updating webhooks.

**IMPORTANT: Execute this command directly. Do NOT generate script files. Simply display the trigger list below.**

## Input

No arguments required

Arguments: $ARGUMENTS

## Instructions

**Display the information directly - do not write code or scripts:**

1. Display the complete list of available webhook triggers with descriptions:

### Message Events
- `MESSAGE_DELIVERY` - Fired when a message is delivered to the recipient
- `MESSAGE_INBOUND` - Fired when an inbound message is received from a contact
- `MESSAGE_SUBMIT` - Fired when a message is submitted for sending
- `MESSAGE_INBOUND_SMART_CONVERSATION_REDACTION` - Fired for smart conversation redaction events

### Conversation Events  
- `CONVERSATION_START` - Fired when a new conversation is started
- `CONVERSATION_STOP` - Fired when a conversation is stopped
- `CONVERSATION_DELETE` - Fired when a conversation is deleted

### Contact Events
- `CONTACT_CREATE` - Fired when a new contact is created
- `CONTACT_DELETE` - Fired when a contact is deleted
- `CONTACT_MERGE` - Fired when contacts are merged
- `CONTACT_UPDATE` - Fired when a contact is updated

### Opt-In/Opt-Out Events
- `OPT_IN` - Fired when a contact opts in for messages
- `OPT_OUT` - Fired when a contact opts out from messages

### Capability Events
- `CAPABILITY` - Fired when channel capability information is updated

### Channel Events
- `CHANNEL_EVENT` - Fired for various channel-specific events

### Unsupported Events
- `UNSUPPORTED` - Fired for unsupported or unknown event types

2. Provide usage examples for common trigger combinations

3. Link to official documentation for more details

## Examples

View all available triggers:
```
/sinch-api-webhooks-triggers
```

## Common Trigger Combinations

**Basic messaging webhook** (most common):
```
MESSAGE_DELIVERY,MESSAGE_INBOUND
```

**Full message lifecycle tracking**:
```
MESSAGE_SUBMIT,MESSAGE_DELIVERY,MESSAGE_INBOUND
```

**Conversation management**:
```
CONVERSATION_START,CONVERSATION_STOP,MESSAGE_INBOUND,MESSAGE_DELIVERY
```

**Opt-in/Opt-out management**:
```
OPT_IN,OPT_OUT,MESSAGE_INBOUND
```

**Comprehensive monitoring**:
```
MESSAGE_DELIVERY,MESSAGE_INBOUND,MESSAGE_SUBMIT,CONVERSATION_START,CONVERSATION_STOP,OPT_IN,OPT_OUT
```

## API Reference

- **Documentation**: https://developers.sinch.com/docs/conversation/api-reference/conversation/tag/Webhooks/
- **Webhook Events**: https://developers.sinch.com/docs/conversation/webhooks/

## Notes

- You can configure multiple triggers for a single webhook
- Not all channels support all event types
- Choose only the triggers you need to reduce unnecessary webhook traffic
- `MESSAGE_DELIVERY` and `MESSAGE_INBOUND` are the most commonly used triggers
- Use `CONVERSATION_START` and `CONVERSATION_STOP` for conversation lifecycle tracking