LinkedIn Bulk Ad Creation API: Missing Deterministic Burst‑Limit Reset Interval

Developers building repeatable integration tests for LinkedIn’s bulk ad creation API need a known burst‑limit reset interval to reliably reproduce rate‑limit scenarios. The endpoint accepts up to 100 ads per request and returns a 202 when queued, but LinkedIn’s documentation only states a per‑app daily quota and a burst‑limit throttle without publishing the exact reset timing for the burst‑limit counter. Empirical observations show the counter resets after an unpredictable window that varies roughly between five and fifteen minutes, influenced by backend load, and the sandbox offers no configuration flag or mock service to fix or simulate this timing. This non‑deterministic behavior makes it difficult to construct stable, repeatable tests.

• Does LinkedIn expose the burst‑limit reset interval through any response header or API endpoint?
• Can a sandbox configuration flag be added to lock the burst‑limit reset to a deterministic value?
• What alternative strategies can provide consistent rate‑limit behavior for automated testing without relying on the undocumented reset window?