Team reverses its adaptive daily API cap after a week, moving limits to per-plan and per-campaign
A developer team shipped a daily API cap that scaled with the previous week's busiest day, then removed it seven days later. The mechanism used one shared counter for the whole product, so a spike in one account could block unrelated paying customers from finding creators for the rest of the day. The team now sets limits per plan, listed on the pricing page, and per campaign, so the account that hits a limit is the one that caused it. Provider-imposed quotas, such as Google's, remain shared because the API key is shared.
This is an AI-generated summary. ShortSingh links to the original source for the complete article.


Discussion (0)
Log in to join the discussion and vote.
Log in