Hey folks, figured I'd start here and post in the other channels if needed. Does anyone have experience running a customer facing API handler through Celigo and successfully set up rate limiting? I'm having an issue with concurrency because I believe that a customer or two is abusing one of my calls for SO Status. Happy to discuss in more detail.

@Tyler Lamparter @matt.graney

I don't think implementing rate limiting in Celigo is a good approach. Celigo isn't designed for that - its main purpose is system integration, not traffic control. If you have a service or interface that customers use to access SO status, you should handle rate limiting within that service instead.

@Sherman Luong while that may have been true before, we now have an API management layer that can sit on top of your Celigo JavaScript apis or API builder apis in Celigo. So if you expose those apis without the management layer, you are correct in that there isn’t a way to do traffic control. That’s where we now have an api management layer, which I linked above, that handles everything you’d need for api traffic control