Possible bug: CURLing the /connections/xxxxx.json endpoint fails

I have 3 environments:

- Local
- Staging
- Production

While on the local env i can implement my login process perfectly (i get the connection token, curl the appropriate 'connections' endpoint and then query my database), in the other two environments (both hosted at AWS) the curl process returns null.

Already checked that the 'connections' endpoint uri is formatted correctly.

Any ideas?

Thank you.



Please sign in to your OneAll account to ask a new question or to contribute to the discussions.

Please click on the link below to connect to the forum with your OneAll account.