Rate Limits and Avoiding Flags#

Wyzie Subs protects the API with per-key and per-visitor limits. Most apps never meet them. This page lists what gets a key flagged, how to get whitelisted and how to stay clear of it.

What Gets a Key Flagged#

• Key on hold (403): very high hourly volume, mostly from datacenter or hosting IPs. See Key on Hold.
• Rate limited (429): a key that keeps going past its limits, hour after hour. Read Retry-After and wait that long.
• Translation already running (429): a key starts a translation while another one is still running. Run one at a time per key.
• Paused (403): our team paused the key after a review. Email [email protected] to have it looked at.
• Missing or invalid key (429): an address that keeps sending bad keys is slowed down for a while. Fix the key and it clears on its own.

Get Whitelisted#

Verify the website you use the key on at sub.wyzie.io/verify with a DNS TXT record or a meta tag. A verified domain reinstates a held key right away and exempts it from automatic holds.

No website, or need higher limits? Email [email protected] with your account email, the first characters of the key (never the whole key), your domain or domains, what your integration does and your expected requests per hour.

Avoid Being Flagged#

• Call the API from your server, not from your users' browsers. For web pages, use a browser-safe key.
• Cache results and reuse files you already downloaded.
• Send a valid key with every request. Do not rotate or share keys.
• On a 429, wait for Retry-After, then retry with backoff and jitter.
• Do not send parallel bursts. Run one translation at a time per key.
• Send a descriptive User-Agent, and a real Origin or Referer from websites.
• Do not enumerate IDs or scrape the catalogue.
• Leave the /download pages to people. Apps should use the API.
• Stay within your plan limits, or upgrade to Pro. Live status: sub.wyzie.io/status.

Flag Notices#