Rate limits and errors

Nimriz applies policy checks and rate limits to protect redirect reliability and reduce abuse risk.

Common causes of failure

• Invalid destination scheme: only https:// (and optionally http:// if policy allows) are accepted.
• Reserved slug: system paths (e.g. api, admin, _health) are blocked on first-party domains.
• Slug policy: slugs below the minimum length may be treated as reserved.
• Quota/rate limit: requests may be throttled or blocked if you exceed plan or abuse thresholds.

Error handling guidelines

• Treat 4xx as a signal to fix inputs (slug, destination, auth) rather than retrying immediately.
• Treat 429 as retryable with backoff.
• For automation, ensure link creation calls are idempotent on your side (so retries don’t create duplicates).