Hey, iāve replied to you over email, but Iāll paste the same answer here in case anyone is having the same issue:
When it comes to tracking from where the API calls are coming from or what API Calls are being made (the body of the API call), we can only do so from these two pieces of information:
ā If a āreferrerā header is included in the request, we can count how many requests had that header and display it in the project usages tab, if the āreferrerā header is not included, we canāt count the request on that tab
ā We always count from which API token the request came from.
ā We always display the IP of where the API request was made from, if provided
So the best way to keep track of where the API requests are coming from, is to create separate API tokens with custom names, and delegate them to specific project sections. Then you will be able to tell from the number of requests per token, which project sections are responsible to the most requests.
You can also adjust the granularity of the sections by creating more API tokens and using them in smaller sections of the project (or even in single requests if you want)
Additionally, to be sure that the API tokens are only being used where they are intended to, you can click on āRegenerate API Tokenā on the top right of the Token page, to invalidate the previous token and generate a new one.