Version 0.1.3 · Registry installation commands use exact versions.
Handle Telegram Stars API 429, Retry-After, and flood wait
Understand the shared IP quota, flood-wait seconds, bounded read retries, and why purchases must not be replayed.
The default fixed-minute quota is 30 requests per IP across all four endpoints, including invalid methods and parameters. At the next minute a new quota window begins; separate application users behind one public IP share the quota.
HTTP 429 returns error_code=FLOOD_WAIT, retry_after, flood_wait, and Retry-After. Waiting is opt-in in these SDKs. They understand numeric or HTTP-date Retry-After and JSON retry hints. Choose bounded retries and a maximum acceptable wait.
HTTP 503 RATE_LIMIT_UNAVAILABLE has Retry-After: 5 in the local contract. This means the rate limiter could not authorize execution, not service-key authentication. Read retries can be enabled; purchases always return an error for human reconciliation rather than automatic replay.
Response
{"ok":false,"error":"Too many requests","error_code":"FLOOD_WAIT","retry_after":42,"flood_wait":42}Continue reading
Handle Telegram Stars API 429, Retry-After, and flood wait · Protect wallet credentials in API integrations · Fragment Donor API and SDK FAQ