Notification Trigger API

/api/v1/notification-triggers is the notification trigger view of the trigger registry. It behaves exactly like the deprecated /api/v1/triggers routes (same auth, same response shapes) but only exposes notification triggers (every provider that is not an action). Any other trigger type returns 404.

Get all notification triggers

curl http://drydock:3000/api/v1/notification-triggers

{
    "data": [
      {
        "id": "smtp.gmail",
        "type": "smtp",
        "name": "gmail",
        "configuration": { "host": "[REDACTED]", "port": 465, "from": "admin@dd.com", "to": "xxx@gmail.com" }
      }
    ],
    "total": 1,
    "limit": 0,
    "offset": 0,
    "hasMore": false
}

Get a notification trigger by id

curl http://drydock:3000/api/v1/notification-triggers/smtp/gmail

To fetch one registered on a specific agent, append the agent name: /api/v1/notification-triggers/smtp/gmail/agent1.

Running a notification trigger

Run a notification trigger with simulated or real container data. Local routes are POST /api/v1/notification-triggers/:type/:name; for containers managed by a remote agent use POST /api/v1/notification-triggers/:type/:name/:agent.

export CONTAINER='{"id":"123456789","name":"container_test","watcher":"watcher_test"}'
curl -X POST -H "Content-Type: application/json" -d "$CONTAINER" http://drydock:3000/api/v1/notification-triggers/smtp/gmail