Tyk support API-level flow control it? I understand that Key-level flow control for Tyk.
Kos @ Tyk Support Team
1 Key can be associated with multiple Policy? May be can’t.
Keys can have many ACL entries or one policy that has many ACL entries.
We’re working towards multiple policies as part of the partitioning feature.
What is ACL entries? Can you show a example?
And the ACL entries is API? May be the Tyk isn’t API-level quotas and rate limiting?
I think each API has its own rate limiting, but multiple APIs can share a Key rate limiting, Tyk routing, then the first route to their own API rate limiting, if not more than their own API settings, and then route to the Key level rate limiting; That is, API rate limiting and Key rate limiting have a priority.
May be sink for this topic?
Quotas and rate limits are per key between keys not at the api level. Api level is planned.
This is a good news for our, but according to your progress, I personally guess will not be released to the 2.4 version of the end of 2017. If sure, this time is too long.