API Throughput Limiting — What It Is and What to Expect

Who This Article Is For

This article applies to clients using the Lightico Public API integration. If you use Lightico through the standalone product, this notice is not relevant to your setup.

Overview

As part of our ongoing commitment to delivering a stable, high-performance experience for our clients, Lightico will be introducing API throughput limiting across all production environments, effective August 15, 2026.

This is an industry-standard safeguard that allows us to protect platform stability and ensure consistent, reliable performance for every client. This change has been designed with your operations in mind. No action is required, and we do not anticipate any impact to day-to-day usage. Limits have been set well above normal operational traffic, so your integration should continue to work exactly as it does today.

This article explains what throughput limiting is, why we're introducing it, and a recommended action your technical team may want to consider.

What Is API Throughput Limiting?

Throughput limiting controls how many API requests can be actively processed at the same time for your account. This is different from a rate limit (which caps how many requests you can send per minute) — throughput limiting is about concurrent in-flight requests, not overall volume.

Throughput limiting applies to authenticated write-based API calls (POST, PUT, PATCH, DELETE).

Why Are We Introducing This?

Delivering a consistent, reliable API experience is a core part of our infrastructure commitment. Throughput limiting is an industry-standard safeguard that allows us to:

• Maintain service quality at all times

• Prevent an unexpected traffic surge from degrading performance

• Ensure predictable, resilient capacity

This control is designed to safeguard platform stability and service availability, not to restrict your usage. Your standard day-to-day operations will not be affected.

Will This Affect My Integration?

We expect no impact to your existing integration. Limits have been set based on observed usage patterns, and standard BAU (business-as-usual) traffic is not expected to reach them.

What Happens If the Limit Is Reached?

If your account reaches its concurrent request limit, additional requests will receive a temporary rejection response:

The Retry-After header tells your integration exactly how long to wait before resending the request.

What Should My Team Do?

Optional but recommended. We recommend that technical teams take this opportunity to confirm that your integration handles 429 responses gracefully — specifically by reading the Retry-After header and retrying after the indicated wait time.

This is considered a best practice for any API integration and ensures your integration is resilient to any transient platform conditions, now or in the future.

If you have a high-traffic event or surge period planned, or if your traffic has historically shown irregular patterns, please coordinate with your Lightico Program Manager in advance so we can ensure your account is fully prepared.

What Lightico Will Do?

Once throughput limiting is in effect, Lightico will actively monitor throughput consumption and error rates across all client accounts. Our goal is to ensure that your operations are not impacted, and to identify and address any anomalies proactively.

Planning for Campaigns or Special Activity

If your team anticipates a period of irregular or elevated API traffic — such as a campaign launch, bulk processing event, or other high-volume activity using Lightico Public API integration — we encourage you to coordinate with your Lightico Program Manager in advance. Early planning allows us to ensure that your activity runs smoothly without interruption.

Key Facts at a Glance

Questions?

If you have any questions about this change or want to discuss your account's API usage patterns, please reach out to your Lightico Program Manager or contact Lightico Support.