Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

aschorr's avatar

Best way to host API routes and client app on same domain

I'm developing a web app, using Laravel to develop the API and admin panel, and another framework for the web client app (next.js/now). I'd optimally like to host them all on the same url: myawesomeapp.com.

Api requests would optimally go to myawesomeapp.com/api/user/ (for example), and the actual web app would route to my next.js, hosted elsewhere, (routes like myawesomeapp.com/profile for example). I assume since much of the server layer is abstracted away if I deploy with Forge, so this wouldn't be possible. However the next best option would be putting my API and admin routes behind subdomains - api.myawesomeapp.com and admin.myawesomeapp.com respectively.

However I'm curious how I could ensure that routes to the root url, simply http://myawesomeapp.com are passed through to my client app (next.js hosted with now)?

0 likes
1 reply
skauk's avatar

The easiest way I think would be to use subdomains, so your API is hosted on api.myawesomeapp.com, for instance, with Forge while your website is on myawesomeapp.com with Next. Another option would be to reverse proxy the API server. There's an example project that shows how to do it with Next specifically.

Please or to participate in this conversation.