-
Task
-
Resolution: Done
-
Normal
-
None
-
None
-
None
-
None
-
5
-
False
-
-
False
-
subs-swatch-2
-
-
Context
Research the Notifications Service to understand available integration options for SWATCH utilization notifications. This is pure research — no working code is required.
SWATCH must notify customers when subscription utilization exceeds thresholds. Before any POC, we need clarity on endpoints, authentication, payloads, and integration patterns.
Out of Scope
- Writing or deploying code
- Building a POC
- Implementing notification logic in SWATCH
Done
- Google Doc with details about:
- Identify API endpoints (REST vs Kafka)
- Document authentication mechanisms (stage/prod)
- Auth setup steps clarified
- Describe payload format and schema requirements
- Identify notification types (email, in-app, etc.)
- Document rate limiting + error handling patterns
- Research local dev/test options
- Error response formats described
- Environment differences (local/stage/prod) captured
- blocks
-
SWATCH-3870 Notifications Service POC
-
- Review
-
- links to