Skip to content

The notification spine: producers post, subscribers get it by text, email or push.

glueReaching people12 operationsid notify

How it sits

Glue chains parts together and keeps the result running. The counts and the links below are from the platform's spec and the other services' own descriptions.

Among the partsfrom the spec
Operations12 GET 8 · POST 3 · DELETE 1
Resources5
Leaned on byno other service names it
Leans onCron, Email, Overseer, SMS, Tapwatch
In recipesnone yet

What it can do

12 operations in 5 resources, as the spec declares them. Each row is one call; paths are relative to the part.

notify

MethodPathDoes
GET/notifyList notifications with their real delivery outcome
POST/notifyPublish a notification
GET/notify/deliveryCan Notify actually deliver right now?
POST/notify/dispatchDeliver pending notifications (Cron tick)
GET/notify/pendingCount undelivered notifications
POST/notify/supersedeRetract undelivered notifications by dedupe_key
DELETE/notify/{notification_id}Delete a notification row
7 operations

health

MethodPathDoes
GET/healthBasic health check
GET/health/detailedDetailed health check
2 operations

hello

MethodPathDoes
GET/api/v1/helloHello world
1 operation

prime

MethodPathDoes
GET/primePrime application caches
1 operation

status

MethodPathDoes
GET/statusService status overview
1 operation

All the partsReaching peopleThe platform's own id for this service is cbnotify.

forge-catalog.json, generated Oct 30, 2026

Anti-cloud. Host local, think global.

Terminal
/terminal