Hi @lio-illumex ,

Have you applied the filter while making the API call?
Try adding all target user IDs to the filter_by.user_ids field in your request body—this might help retrieve the full query history you're expecting.

@lio-illumex I think the API gets a paginated response. you need to hit the API recursively untill it reached the last page. Loop in until you get next_page_token. I would say the best way is to use the databricks SDK. It is simpler then the APIs.

https://databricks-sdk-py.readthedocs.io/en/stable/workspace/sql/query_history.html

The Query History API is scoped to the calling identity, so even with admin rights, service principals can only access their own queries—cross-user access isn't supported.

@SP_6721 I don't filter by user ids in both scenarios, it shouldn't matter
@nayan_wylde I also tried with the SDK but it's the same API call behind the scenes. I made sure it's not a pagination issue.
@jhonm_839 This is so weird. PAT and SP have the same admin rights.... and the admin PAT can see the SP queries.... I don't understand how it's not possible the other way around

Is your workspace Unity Catalog Enabled? If yes try to give the SPN metastore admin permissions. Hopefully it should resolve the issue.