With webhookie you can give your webhook consumers and providers a view of the traffic being sent to their subscriptions.
Traffic is the events sent from a provider to a consumer’s callback. Consumers can view the requests sent to their callback and the status indicating if it was successfully sent to their callback or not. Providers can also view the requests to see which subscriptions successfully received their data.
There are several reasons webhookie stores the traffic. This includes to:
Subscription traffic is your view of the traffic going through subscriptions that you have created as a webhook consumer (WH_CONSUMER).
The traffic table has a row for each unique instance of an event, what we call a span, that is sent to your callback. Including details on the response code that webhookie received.
In the menu for the span, you can see the request and response, as well as, the full details of the processing webhookie has performed. You can also resend the message from this menu.
The number of tries reflects the number of attempts webhookie has made to your callback.
The webhook traffic is your view of the traffic being sent through your webhook API(s). It is only available to users with a webhook provider role (WH_PROVIDER).
The webhook traffic table has a row for each unique instance of an event sent through your API, these are what we call a trace.
Each trace includes a high-level status. The list of statuses include:
For each trace, it’s possible to drill into it to find out the status for each and every span that was generated from it. In the spans you can see the status for each span including the response code received.
For more information:
Powered by BetterDocs