# Rate-limit downstream APIs with separate Task Queues

DevFeed: [Rate-limit downstream APIs with separate Task Queues](<https://devfeed.tech/articles/rate-limit-downstream-apis-with-separate-task-queues-35944.md>)

Original publisher: [Read original article](<https://temporal.io/blog/rate-limit-downstream-apis>)

Author: Cecil Phillip

Published: 2026-05-25T00:00:00Z

Content type: tutorial

Language: en

Sources: [Temporal Blog](<https://devfeed.tech/sources/temporal-blog.md>)

Topics: [rate-limiting](<https://devfeed.tech/topics/rate-limiting.md>), [API](<https://devfeed.tech/topics/api.md>), [Concurrency](<https://devfeed.tech/topics/concurrency.md>), [configuration](<https://devfeed.tech/topics/configuration.md>)

Tags: [apis](<https://devfeed.tech/tags/apis.md>), [concurrency](<https://devfeed.tech/tags/concurrency.md>), [configuration](<https://devfeed.tech/tags/configuration.md>), [queues](<https://devfeed.tech/tags/queues.md>), [rate-limiting](<https://devfeed.tech/tags/rate-limiting.md>), [service](<https://devfeed.tech/tags/service.md>), [temporal-concepts](<https://devfeed.tech/tags/temporal-concepts.md>)

## AI overview

This tutorial explains how to use separate Temporal Task Queues with global and optional per-Worker rate limits, plus concurrency limits, to keep Activities within downstream API quotas and help prevent 429 errors and account issues.

## Source excerpt

Stop hitting 429s on downstream APIs. Use rate-limited Temporal Task Queues to keep Activities under SendGrid, Stripe, and OpenAI quotas.