Notifications
Every message sent to a customer — by a rule or manually — with its delivery status. resend creates a new notification from one that failed (failed or bounced).
| Command | HTTP | Description |
|---|---|---|
notifications list | GET /v1/notifications | List notifications |
notifications create | POST /v1/notifications | Create notification |
notifications get | GET /v1/notifications/{id} | Get notification |
notifications update | PUT /v1/notifications/{id} | Update notification |
notifications delete | DELETE /v1/notifications/{id} | Delete notification |
notifications resend | POST /v1/notifications/{id}/resend | Resend notification |
Examples
--params carries query, path and header parameters (id, page, filters, X-Workspace-Id); --json carries the request body; --fields limits which fields come back — worth using on every list/get to save context. See Global flags for the full reference.
# Failed notifications
kobana dunning notifications list \
--params '{"status": "failed"}' \
--fields "id,person_id,charge_id,channel,status,recipient"
# Resend a notification
kobana dunning notifications resend --params '{"id": "NOTIFICATION_ID"}'
# Delete a notification
kobana dunning notifications delete --params '{"id": "NOTIFICATION_ID"}' --dry-run
Next steps
- Notification channels
- Schema introspection — every parameter this resource accepts.