Notification API Endpoints
S
Steven Rowley E.J.D.
Client communication and responsiveness is our #1 priority this year. We have relied on the system notifications but that is still allowing many of our target 'responsiveness' events to go unnoticed. Issues within the notification system as it is currently built out is likely the cause. If the notifications for events that are shown on the 'Manage Notifications' screen had API endpoints, they would provide users with excellent workarounds while the deeper foundational work behind notifications are built out. We would prioritize Client Communication Notifications, then Client Submission Notifications, and then whatever makes sense for the others. These two priorities allow us to focus on our clients and building a rock solid relationship as excellent client focused providers.
Log In
A
Aaron Sendrovits
+1 — this would be a great bridge. The notification feed already captures the exact events integrations need (client messages, client submissions). Exposing it via API — even just "list my notifications since X" — would let external dashboards surface client responsiveness in near-real-time without dedicated webhooks for every resource. We'd use this immediately.