Uploaded image for project: 'Subscription Watch'
  1. Subscription Watch
  2. SWATCH-3869

Research Notifications Service integration patterns and document API usage

XMLWordPrintable

    • Icon: Task Task
    • Resolution: Done
    • Icon: Normal Normal
    • None
    • None
    • None
    • None

      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

              rh-ee-tlencion Tommaso Lencioni
              lburnett0 Lindsey Burnett
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: