Skip to main content
Browse Documentation

View webhook activity logs

Created by r.saunders, last modified by r.bromley on 08 Apr 2021

We keep a log of all activity for each webhook for 30 days in your project. Activity logs can be really helpful when you want to troubleshoot why a webhook may not have been successful.

To view the activity logs of a webhook you will need to be a System Administrator or be a member of a role with webhook permissions.

  1. Navigate to the Webhooks screen in Settings by pressing the Settings button in the sidebar, followed by Webhooks.
  2. Locate the Webhook you want to view the activity for in the list and press the Action button denoted by the triple dot.
  3. Select Activity logs from the menu.
  4. The activity logs will be displayed for the webhook.

Activity log listing

The following information is displayed in the activity log listing:

  • Webhook URL – This is the endpoint URL you set in the webhook. The URL that you see may vary if you've templated the URL with values such as the entry ID or other resource values, for example"1a4bc60a-a5c1-4030-944f-64b1d90f3431".
  • Resource – The type of resource the webhook was triggered by. This could be Entries, Content types, Components, Assets, Nodes, Users or Groups.
  • Event – The type of event that raised the webhook event. This could include Created, Updated, Published, Deleted, Unpublished, workflowStateChange, workflowEventRaised.
  • Date / time – Specifies the date and time when the webhook was initially triggered.
  • Status – Specifies the status of the triggered webhook and whether it was successfully triggered, denoted by the HTTP status code of 200, or if any error has occurred, denoted by status code 400. You may also see a status of In progress. This occurs when the webhook is initially triggered and awaiting a HTTP response.
  • Response time – The response time from the endpoint that resulted in a successful 200 HTTP status code.
  • Attempts – In the event of a failure, or if a session timeout occurs (the webhook request timeout is 10 seconds), the webhook will immediately retry sending data to the destination URL again a further 9 times in a 24 hour period using an exponential backoff strategy.

View call details

To view the details of the webhook call, click on the call details link. It will display the Request Details of the webhook call as well as the Response Details received.

Cycle through retries

When the webhook has had a number of retries you can cycle through the call details of each request and response using the previous and back buttons in the call details toolbar.

Necessary Cookies
These cookies are necessary for this website to function correctly. They are set when you perform certain actions on the site, such as creating an account, logging in, changing your privacy preferences or submitting a form. You can block these cookies in your browser, but this will stop parts of the site from working properly.
Functional Cookies
These cookies allow the website to provide extra functionality and more personalised experiences. They may be set by us or by third party providers whose services we have added to our pages. If you choose not to allow these cookies, these services may not work correctly.
Analytical Cookies
These cookies record anonymous data on how visitors use our website to help us monitor how well our website works. This data includes how many people have looked at specific pages, how long visitors stay on the site, and what devices they use. We use this data to identify changes that we could make to improve your experience and make our website more efficient.
Marketing Cookies
We set some cookies so you are shown more relevant marketing content. These include cookies from third-party advertising networks to show you different adverts on their services if you have previously visited our site. If you choose not to allow these cookies, you may experience less relevant advertising on other sites.