Uploaded image for project: 'Blesta Core'
  1. Blesta Core
  2. CORE-5190

Webhooks: Add information about the event to the headers of outgoing requests

        Details

        • Type: Improvement
        • Status: Closed
        • Priority: Major
        • Resolution: Fixed
        • Affects Version/s: 5.10.0-b2
        • Fix Version/s: 5.10.0
        • Component/s: Plugins
        • Labels:
          None

          Description

          When a webhook is triggered, it sends the data to the endpoint, but if we have many events going to the same endpoint, we don't know what event it is for. The event name should be included in the webhook headers.

          X-Blesta-Event: Clients.addNoteAfter
          X-Webhook-Id: 1
          User-Agent: Blesta-Webhook

          X-Blesta-Event contains the event name.
          X-Webhook-Id contains the ID of the webhook we created
          User-Agent because why not, we should be able to tell

            Activity

            Ascending order - Click to sort in descending order
            admin Paul Phillips created issue -
            jonathan Jonathan Reissmueller made changes -
            Field Original Value New Value
            Rank Ranked higher
            admin Paul Phillips made changes -
            Sprint 5.11.0 Sprint 1 [ 194 ]
            admin Paul Phillips made changes -
            Rank Ranked lower
            jonathan Jonathan Reissmueller made changes -
            Status Open [ 1 ] In Review [ 5 ]
            Resolution Fixed [ 1 ]
            abdy Abdy Franco made changes -
            Remaining Estimate 0 minutes [ 0 ]
            Time Spent 13 minutes [ 780 ]
            Worklog Id 17114 [ 17114 ]
            abdy Abdy Franco made changes -
            Status In Review [ 5 ] Closed [ 6 ]

              People

              • Assignee:
                jonathan Jonathan Reissmueller
                Reporter:
                admin Paul Phillips
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:
                  Fix Release Date:
                  5/Jun/24

                  Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0 minutes
                  0m
                  Logged:
                  Time Spent - 13 minutes
                  13m

                    Agile