this is a common concern when working with containerized apps on cloud platforms like AWS, where outbound IPs can change dynamically depending on region or scaling.
As of now, FatSecret does not officially restrict access based on the source IP for outbound requests to their API. So yes, in most cases, you can safely allow 0.0.0.0/0 and ::/0 as outbound rules in your security group or network configuration — especially if you’re consuming their API and not hosting a callback URL that FatSecret needs to reach.
However, if you're dealing with webhooks or need FatSecret to call your endpoint, then IP whitelisting could be more relevant — and in that case, you'd need a fixed IP (Elastic IP, NAT Gateway, etc.).
I was dealing with a similar network policy while setting up nutrition tracking with my team (right after ordering menu marugame udon, of course 😅) — and went with 0.0.0.0/0 temporarily. Everything worked smoothly, and no IP-related blocks from FatSecret were observed.
Still, for absolute confirmation, it’s worth emailing their support or checking with an official FatSecret rep.
Agar tu chahe toh isko ek forum post ya email draft me bhi convert kar deta hoon — just say the word 💡