You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This issue is not a question, general help request, or anything other than a feature request directly related to Unkey. Please ask questions in our Discord community: https://unkey.dev/discord.
Is your feature request related to a problem? Please describe.
I want to get access to the IPs from where key verifications are done so that I can keep track of keys not being used by multiple people.
Describe the solution
Having access to the IP address of the verification request and possibly their region.
Describe alternatives you have considered (if any)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered:
Is it possible to access via the API? I would like to write a script and form insights on that.
I realize that I should have done prior research before opening this issue 😅. It seems like this is already possible. Feel free to close this issue.
Currently it's not possible via the API only through the dashboard itself, we do have plans to enrich the analytical data more in the API so you could do this in the future but not currently.
Preliminary Checks
I have reviewed https://unkey.dev/docs for existing features that would solve my problem
I have searched for existing feature requests: https://github.com/unkeyed/unkey/issues
This issue is not a question, general help request, or anything other than a feature request directly related to Unkey. Please ask questions in our Discord community: https://unkey.dev/discord.
Is your feature request related to a problem? Please describe.
I want to get access to the IPs from where key verifications are done so that I can keep track of keys not being used by multiple people.
Describe the solution
Having access to the IP address of the verification request and possibly their region.
Describe alternatives you have considered (if any)
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: