Reliability and Operations

Understand the public operational surface around status visibility, rate limits, webhook handling, and how to design your integration conservatively.

Status visibility

Use status.zenmanage.com as the public source of truth for current service health before you assume an integration issue is local to your application.

Rate limits

The public API reference documents a limit of 60 requests per minute. If your architecture would exceed that, design around caching, SDK-based rule evaluation, or contact the Zenmanage team before launch.

Webhook operations note

Webhook failure notification and retry timing are not fully specified in current public docs. For production use, assume your consumer must be resilient on its own and that replay-safe behavior is required.

Conservative production posture

Always provide default values in code for every flag read.
Use webhook-driven cache invalidation if stale values would create material risk.
Keep a simple kill-switch path for critical production features.
Monitor the public status page during incident triage.

This posture lets your application degrade gracefully even when the surrounding network or operational environment is imperfect.

Next step

Take the next integration step in your own stack.

Start with the quickstart that matches your runtime, then return to the reference pages when you need exact request and payload details.

View quickstarts Start free trial