So either copy it into the api group, or add it to protected $middleware array and remove it from web group. The protected $middleware group runs for all requests, where web is only web routes and api is api routes. Basically you don't want it to load twice.
A session is seperate for each client and a client is usually a browser.
However i my project there are 2 laravel projects.
One project is a gateway which the users (via their browsers) connect to directly.
The second other is the API which actually provides the services and has access to various datasources
The gateway project makes all HTTP requests to the API project
This means there is only one "client" connecting no matter how many users there are
or put another way
each user does not have his own unique session with the API
Then it really sounds like this "package" that requires session, isn't suitable to use in your api. I understand what session is. Normally you don't use one with apis, but you asked...
Cronix
Indeed
but we did not realize that this package required session until the very last stage of developing the feature which we want to use it for