Generate Undelivered Webhooks Report

This API retrieves a list of webhooks which Bringg sent but did not receive a confirmation, during a specified time period. Bringg tries to send a webhook three times. After a third failed attempt, if it hasn't received the expected sent-response confirmation from the recipient system, it would join this report.

This API returns its report as a link to a CSV file which is behind a login either via email or a callback_url. You must enter one of these choices in your request parameters.

The API sends its response in the email or callback_url containing the secure link (behind login) to the file. You can manually access the report if you sign in, or you can do it automatically as part of your programming with the following procedure:

  1. Copy the UUID after the reportId from the callback_url response of this API. For example, if the response is https://dashboard.bringg.com?reportId=be5fefa1-9b7e-406c-8449-d167a6672d22, the reportId is be5fefa1-9b7e-406c-8449-d167a6672d22
  2. Retrieve your login authentication_token from the response to:
    curl -H "Content-Type: application/json" -XPOST https://admin-api.bringg.com/tokens -d'{ "email":"<USER_EMAIL>", "password": "<PASSWORD>" }'
  3. Obtain the link to the report (CSV file) by using the reportId from the callback_url as detailed in step 1 and the authentication_token from step 2:
    curl -v -H "Authorization: Token token=VALUE_OF_AUTHENTICATION_TOKEN" https://admin-api.bringg.com/reports-service/v1/report_execution\?uuid\=reportId

The response is a JSON containing a URL to a short-lived (30 days) CSV file which you can download.

Language