Revert a feature to a specific revision
Deprecated. Use POST /v2/features/:id/revert instead.
Restores a previously published revision and immediately publishes the result as a new revision. The caller needs Revert access for every affected environment. When approval is required, the request is allowed only if the caller holds the FlagsBypassApprovals policy, or the organization enables either “REST API always bypasses approval requirements” or “Allow reverts without approval”.
If the restored values no longer match the Feature Flag’s current value type or JSON schema, the API returns 422 with warnings. Send "ignoreWarnings": true to acknowledge those warnings and continue.
Authorizations
If using Bearer auth, pass the Secret Key as the token:
Path Parameters
The id of the requested resource
Body
Set to true to acknowledge the warnings listed in a blocked response and continue. This covers experiment guards, locked dependents, and references affected by an archive. When the organization treats schema failures as warnings, it also covers schema and invariant warnings. It never bypasses a rejected Custom Hook. On revision publish endpoints, it can also force-publish an out-of-date draft when the caller has Bypass draft approvals access.
Set to true to publish despite schema validation errors, failed invariants, or schema changes that invalidate dependent resources. This does not bypass a rejected Custom Hook; use skipHooks for that. The caller must have Bypass draft approvals access for Feature Flags, Configs, and Constants in every Project. Otherwise, this field is ignored.
Set to true to publish despite a Custom Hook rejection. This does not bypass schema validation; use skipSchemaValidation for that. The caller must have Bypass draft approvals access for Feature Flags, Configs, and Constants in every Project. Otherwise, this field is ignored.

