Webhook for user search and API endpoint for user search requests #5036

Closed
opened 2026-02-05 09:35:39 +03:00 by OVERLORD · 1 comment
Owner

Originally created by @MrLeaw on GitHub (Nov 3, 2024).

Describe the feature you'd like

  1. It would be nice to have a webhook that fires on every search request made by a user, and/or an API endpoint which responds with all search requests in a given timespan (last 24 hours, ...)

Describe the benefits this would bring to existing BookStack users

We would like to check what our employees are looking for, and use this data to analyze how we can improve the layout of the wiki, which keywords we could add to pages

Can the goal of this request already be achieved via other means?

no

Have you searched for an existing open/closed issue?

  • I have searched for existing issues and none cover my fundamental request

How long have you been using BookStack?

Under 3 months

Additional context

No response

Originally created by @MrLeaw on GitHub (Nov 3, 2024). ### Describe the feature you'd like 1. It would be nice to have a webhook that fires on every search request made by a user, and/or an API endpoint which responds with all search requests in a given timespan (last 24 hours, ...) ### Describe the benefits this would bring to existing BookStack users We would like to check what our employees are looking for, and use this data to analyze how we can improve the layout of the wiki, which keywords we could add to pages ### Can the goal of this request already be achieved via other means? no ### Have you searched for an existing open/closed issue? - [X] I have searched for existing issues and none cover my fundamental request ### How long have you been using BookStack? Under 3 months ### Additional context _No response_
OVERLORD added the :cat2:🐈 Possible duplicate label 2026-02-05 09:35:39 +03:00
Author
Owner

@ssddanbrown commented on GitHub (Nov 3, 2024):

Thanks for the request @MrLeaw, but I'm going to close this off as a duplicate of existing issue #1000 since I feel the fundamental request (insight into search terms) is much the same and this would be an extension of supporting that.

Can the goal of this request already be achieved via other means?
no

As some other ways this could be achieved:

  • You could scan/extract this from webserver access logs, extract the query parameters from the URL of search requests.
  • You could use an external analytics solution (plausible, Google Analytics, Fathom etc...) to track/record this info.
@ssddanbrown commented on GitHub (Nov 3, 2024): Thanks for the request @MrLeaw, but I'm going to close this off as a duplicate of existing issue #1000 since I feel the fundamental request (insight into search terms) is much the same and this would be an extension of supporting that. > Can the goal of this request already be achieved via other means? > no As some other ways this could be achieved: - You could scan/extract this from webserver access logs, extract the query parameters from the URL of search requests. - You could use an external analytics solution (plausible, Google Analytics, Fathom etc...) to track/record this info.
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/BookStack#5036