I'm using the new Guard authentication for authenticating API requests. Diving into the Guard code, I see that it triggers a InteractiveLoginEvent once the authentication was successful. My application listens for that event to track user logins, so I don't necessarily want it to be triggered for API requests.
I was wondering whether there was a way to bypass the event being dispatched in Guard for API authentication? Or did I misunderstand the purpose of the InteractiveLoginEvent?