One obvious workaround is to creates two differently named routes for the same controller/method, one with an api prefix, wrapped in a token auth group and one without for your frontend. More work to maintain and obvious duplication which is kinda sloppy but it would achieve what you're looking for.
Sign in to participate in this thread!
The Laravel portal for problem solving, knowledge sharing and community building.
The community