Consuming REST API in PHP with Guzzle

Session or database is fine. It depends on the livecycle of the token. Is it a temporary token then store it in the session. Is it a token you need to use the rest of the year? Store it in the database. Make sure you encrypt the token before you store it ;)

You can also use local storage or cookies. The difference between local and session storage can be seen at https://stackoverflow.com/questions/5523140/html5-local-storage-vs-session-storage.

@bobbybouwmann Thanks. The token has a lifespan after which it is invalid.

@CJJ Why should I use local/session storage at the backend? The purpose was to consume it using PHP and not at the frontend.

@ultrasamad My apologies, didn't realise we were talking blade. I posted without thinking. I always use a decoupled frontend.

You can put it in either place. When you reboot your server you lose the token in the session, in the database it's always there :)

@bobbybouwmann I realized I could not write to the session. No error is returned but it wasn't just working. But when I tried it on the web routes, it works. So I was thinking probably session storage is disabled for api routes...

Any help on that?

@ultrasamad It's disabled by default for API's by Laravel. If you open ' app/Http/Kernel.php you can see that the api group does not have a session middleware and that the web group does have a session middleware.

Your API does not need a session most of the time. If it does you can simply add the session middleware and you're done!

@bobbybouwmann Thanks for pointing that out.