ColorfulClouds · Rate Limits

Colorfulclouds Rate Limits

Caiyun Weather API rate limits are scoped per API token (or per App Key on v3). The free developer tier is documented at approximately 400 requests per day; paid tiers raise the daily quota in published bands purchased on the Open Platform. Per-second / per-minute throttling beyond the daily quota is enforced by the gateway but the precise burst rate is not publicly documented and varies by tier. Token rotation, App Key + App Secret signing (v3), and exponential backoff on 429/503 are the recommended consumer-side policies.

Colorfulclouds Rate Limits is the machine-readable rate-limit profile for ColorfulClouds on the APIs.io network, conforming to the API Commons Rate Limits specification.

It captures 4 rate-limit definitions, measuring requests_per_day, requests_per_second, and tile_requests_per_month.

The profile also includes 5 backoff/retry policies defined and response codes documented for unauthorized, throttled, quotaExceeded, serverError, and unavailable.

Tagged areas include Rate Limiting, Weather, and Quota.

4 Limits Throttle: 429 Quota: 429
Rate LimitingWeatherQuota

Limits

Free tier daily quota token
requests_per_day · day
400
Documented free-tier ceiling per API token. Counted across all v2.6 endpoints (realtime, minutely, hourly, daily, weather, air-quality, alert) under the token.
Paid tier daily quota token
requests_per_day
see operator console / tier-specific
Tier-specific daily quotas (10k, 100k, 1M bands) are sold through the Open Platform; exact band sizes and per-tier pricing are visible only to authenticated tenants.
Gateway burst throttling token
requests_per_second
see tier-specific QPS
Per-second / per-minute burst throttling is enforced server-side but not publicly documented. Plan for token-bucket backoff on 429.
Precipitation map tile fetches token
tile_requests_per_month
tier-specific
Map raster tile requests are usually metered separately from JSON endpoint requests on paid tiers.

Policies

Exponential backoff on 429
Retry on 429 with exponential backoff (start 1s, double up to 30s ceiling) and a jittered delay. Respect Retry-After when present.
Token rotation and App Key signing
For v3 deployments, use App Key + App Secret signing instead of bare tokens to limit leakage risk. Rotate tokens periodically via the Open Platform console.
Per-token scoping
Quotas are scoped to the token (or App Key); split traffic across tokens for high-volume consumer apps with distinct billing owners.
Cache realtime + minutely responses
Realtime is meaningful only at sub-minute resolution; cache responses for 30-60s per coordinate to absorb burst load and stay within quota.
Coordinate quantization
Quantize lng,lat to ~1km grid before requesting to maximize cache hits across users in the same area without losing meaningful precision.

Sources