Approval Workflows

Approval workflows add a review step before flag changes are applied, providing an extra layer of safety for production environments.

How It Works

A developer creates an approval request with the desired change
The request enters a pending state
An admin or owner reviews the request
If approved, the change is automatically applied

Creating an Approval Request

bash

curl -X POST https://api.featuresignals.com/v1/approvals \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"flag_id": "flag-uuid", "env_id": "production-uuid", "change_type": "enable_with_rollout", "payload": {"enabled": true, "percentage_rollout": 5000}}'

Reviewing

bash

# Approve
curl -X POST https://api.featuresignals.com/v1/approvals/$APPROVAL_ID/review \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"action": "approve", "note": "Looks good for 50% rollout"}'

# Reject
curl -X POST https://api.featuresignals.com/v1/approvals/$APPROVAL_ID/review \
  -H "Authorization: Bearer $TOKEN" \
  -d '{"action": "reject", "note": "Needs more testing in staging first"}'

Rules

Only pending requests can be reviewed
Self-approval is not allowed
Only owner or admin roles can review

Next Steps