Webhooks Management

Web interface configuration only

Webhooks must be created and configured from the web dashboard by a user with STAFF role (ADMIN or OWNER).

This API reference page is maintained for documentation purposes, but these endpoints are not accessible via standard API keys.

This section documents internal endpoints used by the web interface to manage webhooks.

Required Access

• Authenticated connection via web interface
• ADMIN or OWNER role

List Webhooks

curl https://mc-prd.duckdns.org/api/v1/staff/webhooks \
-H "X-API-Key: YOUR_API_KEY"

Response 200:

{
  "data": [
    {
      "id": "wh_123",
      "url": "https://votre-app.com/webhooks/moncreneau",
      "events": ["appointment.created", "appointment.cancelled"],
      "secret": "whsec_xxxxx",
      "active": true,
      "createdAt": "2026-01-10T12:00:00Z"
    }
  ]
}

Create a Webhook

curl -X POST https://mc-prd.duckdns.org/api/v1/staff/webhooks \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "url": "https://votre-app.com/webhooks/moncreneau",
  "events": ["appointment.created"],
  "secret": "votre_secret_webhook"
}'

Update a Webhook

curl -X PUT https://mc-prd.duckdns.org/api/v1/staff/webhooks/wh_123 \
-H "X-API-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{
  "events": ["appointment.created", "appointment.cancelled", "appointment.updated"],
  "active": true
}'

Delete a Webhook

curl -X DELETE https://mc-prd.duckdns.org/api/v1/staff/webhooks/wh_123 \
-H "X-API-Key: YOUR_API_KEY"

Test a Webhook

curl -X POST https://mc-prd.duckdns.org/api/v1/staff/webhooks/wh_123/test \
-H "X-API-Key: YOUR_API_KEY"

Response 200:

{
  "success": true,
  "httpStatus": 200,
  "responseTime": 320,
  "message": "Webhook test successful"
}

Available Events

• appointment.created - New appointment created
• appointment.updated - Appointment modified
• appointment.cancelled - Appointment cancelled
• appointment.confirmed - Appointment confirmed

See Webhooks for more details.