Skip to content

security

Intended Documentation

Emergency Controls

Trigger and review emergency control actions for tenant and environment containment.

advanced1 min readimplemented

Emergency Controls#

Emergency controls are exposed through enterprise admin endpoints and are fully audited.

Read Current Emergency State#

  • GET /admin/emergency-controls?tenantId=<tenant>

Invoke Emergency Action#

  • POST /admin/emergency-controls/:action

Supported actions:

  • tenant_halt
  • tenant_resume
  • environment_halt
  • environment_resume
  • connector_pause
  • connector_resume
  • token_revoke

Request body schema:

  • tenantId (required)
  • reason (required)
  • environmentKey (optional)
  • targetRef (optional)
  • metadata (optional)
bash
curl -X POST https://api.intended.so/admin/emergency-controls/tenant_halt \
  -H "Authorization: Bearer mrt_live_abc123" \
  -H "x-tenant-id: tenant_acme_prod" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_acme_prod",
    "reason": "Containment for INC-2026-0342"
  }'

Token Revocation Example#

bash
curl -X POST https://api.intended.so/admin/emergency-controls/token_revoke \
  -H "Authorization: Bearer mrt_live_abc123" \
  -H "x-tenant-id: tenant_acme_prod" \
  -H "Content-Type: application/json" \
  -d '{
    "tenantId": "tenant_acme_prod",
    "targetRef": "cred_123",
    "reason": "Credential compromise suspected"
  }'

Warning

Emergency actions are fail-closed and high impact. Always include an incident reference in reason for audit traceability.

Next Steps#