DNA Sequence API limit changes

To protect the stability and performance of the DNA Sequence API, we're introducing some new limits on the number of sequences that can be processed at once. The /dna-sequences:auto-annotate, /dna-sequences:autofill-parts, /dna-sequences:autofill-translations, and /dna-sequences:autofill-transcriptions endpoints will be limited to 2000 sequences in a single request, and will be subject to throughput rate limiting. These changes will go live on October 7th 2024.

What’s changing?

Previously, a number of the DNA Sequence API endpoints were subject to overly-permissive limits which resulted in performance and stability issues during periods of high traffic. This includes the following endpoints:

Going forward, these endpoints will be subject to Data and Throughput limits more consistent with the rest of the Developer Platform. Specifically, each endpoint will now have a bulk operation limit of 2000 sequences per request. Additionally, these endpoints will be subject to throughput rate limiting in order to better protect the stability of Benchling's systems.

🚧
Isn't this a breaking change?
Due to the impact on the performance and stability of Benchling's systems, these limits are being implemented on an expedited timeframe. For more information, check out Benchling's Stability Guidelines

To avoid disruption, it's important to make sure all integrations are limiting the number of sequences being processed in any single request, and avoiding processing large numbers of sequences continuously. Additionally, implementing proper rate limit handling (e.g. exponential backoff) will help ensure that integrations operate gracefully within Benchling's rate limits.

When is this happening?

These changes will go live on October 7th 2024.

What’s changing?

🚧Isn't this a breaking change?

When is this happening?

🚧
Isn't this a breaking change?