Call different slim framework URL/REST API under the hood?

Redirecting from service2.com to service1.com and then back to service2.com should be transparent. At most a user will see a notification in the status bar that data is being loaded from service1.com.

I didn’t know it was possible redirect a POST request, but apparantly it should work with a 307 status code. I haven’t checked though.

Instead of redirecting, you can also issue a POST request from service2 to service1 using cURL or guzzle. But if you need cookies to be set for the service1.com domain, you will have to redirect the user in some form.