Answers.Body: <p>You need to give yourself &quot;CiviCRM: view debug output&quot; permission in the CMS.</p>
  <p>Also if it's not obvious, you have to run the search first before it appears.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-22T17:35:01.217Z
Answers.Text: Just what I needed - thanks!
Answers.UserDisplayName: dposorio
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2021-04-09T05:12:17.667Z
Answers.LastActivityDate: 2024-10-15T23:50:12.770Z
Answers.LastEditDate: 2024-10-15T23:50:12.770Z
Answers.UserDisplayName: Demerit
Body: <p>I was following along the <a href="https://www.youtube.com/watch?v=5WAAaBsJQsE&amp;list=PLjSU7YfE0E028kuK948i7_qxUlbHZbfJR&amp;index=1" rel="nofollow noreferrer">1st video</a> of the <a href="https://www.youtube.com/playlist?list=PLjSU7YfE0E028kuK948i7_qxUlbHZbfJR" rel="nofollow noreferrer">SearchKit playlist on Youtube</a>. And approximately 38 min in, the presenter shows how one can see the underlying API code or SQL code for a given search. It looks like he simply expanded on a tab, Query Info. However this is not available for me on my Buildkit site and I'm wondered how to enable this.</p>
  
Tags: <searchkit>
Title: How to view SearchKit's API and SQL
ThreadText: # How to view SearchKit's API and SQL
  
  (Asked by: username_0 on 2021-04-08)
  
  I was following along the [1st video](https://www.youtube.com/watch?v=5WAAaBsJQsE&list=PLjSU7YfE0E028kuK948i7_qxUlbHZbfJR&index=1) of the [SearchKit playlist on Youtube](https://www.youtube.com/playlist?list=PLjSU7YfE0E028kuK948i7_qxUlbHZbfJR). And approximately 38 min in, the presenter shows how one can see the underlying API code or SQL code for a given search. It looks like he simply expanded on a tab, Query Info. However this is not available for me on my Buildkit site and I'm wondered how to enable this.
  
  **Tags:** searchkit
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2021-04-09. Score: 4 | Accepted answer
  
  You need to give yourself "CiviCRM: view debug output" permission in the CMS.
  
  Also if it's not obvious, you have to run the search first before it appears.
  
  > **Comments:**
  > **username_0**: Just what I needed - thanks!  
  
  ---
  
  