MyStars FaaS — Fulfilment API · Rate Limits
Mystars Faas Fulfilment Api Rate Limits
Mystars Faas Fulfilment Api Rate Limits is the machine-readable rate-limit profile for MyStars FaaS — Fulfilment API on the APIs.io network, in the API Commons Rate Limits shape.
It captures 4 rate-limit definitions.
Limit state is signalled in the RateLimit-Limit, RateLimit-Remaining, RateLimit-Reset, and Retry-After response headers.
Tagged areas include Telegram, telegram-stars, telegram-premium, Payments, and Cryptocurrency.
4 Limits
RateLimit-LimitRateLimit-RemainingRateLimit-ResetRetry-After
Transcribed from the provider's documentation on 2026-09-03 — mystars.tg/docs.
View Source
Telegramtelegram-starstelegram-premiumPaymentsCryptocurrencyTONgramUSDTFintechfulfilmentDigital GoodsNon-Custodialno-kyc
Limits
per-tenant, /v1 read endpoints
60/1 minute
Default per-minute request budget; read the live ceiling from RateLimit-Limit rather than hard-coding.
per-tenant, order lifecycle (createOrder, getOrder, cancelOrder)
60/1 minute
A separate bucket of the same per-minute size, isolated from the read budget - a burst of pricing/catalog reads can never throttle order create, poll, or cancel.
per-tenant probe cap (getPricing, getPricingBatch, checkRecipient)
60/1 minute
Tighter cap in addition to the general budget because each call drives an upstream price/eligibility lookup. A batch pricing call counts as one unit. (Raised 10 -> 30/min in v1.5.0; the current docs and spec state 60/min.)
per-tenant daily order cap + per-recipient concurrent-order guard (createOrder)
Optional daily order cap and a flood guard on concurrent orders to the same @username; numbers are not published. These 429s carry the error envelope only, without RateLimit-* headers.
Work with this as data
Every rate limit here is available over the APIs.io API and to AI agents over MCP.