So I've deployed my entire Payload 3.0 app in one repo to vercel, but concerningly I cant hit the /api endpoint of my site, nor can I visit the admin panel at /admin. In localhost it works of course. I have my domain name as my next public API url so all requests go to that endpoint and /api. It's almost like Payload is missing in prod. Coming here because I'm having trouble finding anything on this problem in relation to Payload 3.0. Thank you and any help is appreciated! 
#/api endpoint not exposed on prod
1 messages · Page 1 of 1 (latest)
Help is on the way! To mark it as solved, use the /solve command. In the meantime, here are some existing threads that may help you:
Documentation:
- Stripe Plugin - Endpoints - Stripe REST Proxy
- REST API - Custom Endpoints
- Using the Payload Auth Middleware
- Authentication Operations - Verify by Email
- Stripe Plugin - Endpoints
Community-Help:
Sounds like it might be a cors issue
https://payloadcms.com/docs/beta/configuration/overview#config-options
I'll check that out
For anyone who sees this, my digital ocean database was only allowing trusted IP's, and since my project isnt on a droplet, I had to allow all IP's to be able to connect to my database which isn't super smart. So that's the fix if your project builds but theres no /api endpoint. Just make sure if you do this, secure it in a couple other ways, but for all i know managed databases by digital ocean are pretty secure off rip.