Back to Blog
tip

429 Too Many Requests for GetPlayerSummaries

Steam Tightens the Screws: Why You’re Seeing More 429 Too Many Requests for GetPlayerSummaries (Since 1 June 2025) Since 1 June 2025, developers have faced a sudden wave of 429 errors when calling ISteamUser/GetPlayerSummaries.

Published recently

Steam Tightens the Screws: Why You’re Seeing More 429 Too Many Requests for GetPlayerSummaries (Since 1 June 2025)

Since 1 June 2025, developers have faced a sudden wave of 429 errors when calling
ISteamUser/GetPlayerSummaries. If your logs now show something like:

pgsqlKopierenBearbeitenHTTP/1.1 429 Too Many Requests
Server: nginx
Content-Type: text/html
Retry-After: 60

you’re not alone—Steam quietly lowered its rate-limits on player-profile data and now throttles far more aggressively.

What Changed?

Until 31 May 2025From 1 June 2025≈ 100 req/s tolerated, bursts ~1 000 req/min | ≈ 25 req/s (best estimate) with a hard burst lock—exceed it and you hit 429 instantly
Retry-After rarely present | Retry-After almost always 60–120 s
Throttling focused on inventory endpoints | Profile endpoints throttled just as hard

Bottom line: Steam now treats profile data almost as sensitively as trading and inventory information.

Why the 429 Response?

429 Too Many Requests signals that you’ve exceeded an (undocumented) quota:

  1. Your traffic crosses Steam’s threshold.
  2. Steam replies with 429, often including a Retry-After delay.
  3. Continual retries keep you locked out—or escalate to a temporary 503 ban.


A Simpler Path: Use Our Steam Profile API

Instead of wrestling with shifting Steam limits, you can integrate our Profile API and let us handle throttling, retries, and edge cases behind the scenes.

  • Drop-in REST interface—no code overhaul required.
  • Fair usage tiers for staging, testing, and production workloads.
  • Clear documentation and responsive support.

Focus on building your app; we take care of the profile plumbing.

Takeaways

  • 429 Too Many Requests for GetPlayerSummaries is the new normal after 1 June 2025.
  • Steam’s tighter limits now hit profile endpoints as much as inventory ones.
  • Smart throttling, caching, and batching can cut error rates—but if you want a hassle-free option, our Profile API provides a reliable alternative.


Have questions about getting started? Reach out—our team is ready to help you keep shipping smoothly. 💙