---
title: "NVIDIA Mission Control autonomous recovery trigger (W13)"
method: POST
path: "/api/maintenance/nmc-trigger"
tags: ["Maintenance"]
---

# NVIDIA Mission Control autonomous recovery trigger (W13)

`POST /api/maintenance/nmc-trigger`

## Request

- Base URL: `https://api.fiber.ac` (the document declares no server; this is the origin it was published from)
- URL: `https://api.fiber.ac/api/maintenance/nmc-trigger`
- Auth: none declared

Forwards a port replacement / hardware-recovery request to NVIDIA Mission Control's autonomous recovery API (NMC 2.0+). Closed-loop from FIBER risk → NMC ticket → physical action.

Body: {"switch_name":..., "port_name":..., "reason": str (optional), "risk_score": int (optional), "job_ids": [list, optional]}

Behaviour:
  • Dry-run if FIBER_NMC_URL / FIBER_NMC_TOKEN env vars unset — returns the     payload that would be sent and `dry_run: true`.
  • Live call sends POST {NMC_URL}/api/v1/recovery/trigger with bearer auth.

Use risk≥80 from the 3-tier engine to drive automatic invocation; viewer or operator role keys can call this — actual execution happens server-side under the FIBER service account scoped to NMC.

## Request body

- object

## Response `200`

NMC ticket ID + status, or dry-run preview

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/fiber-ac/apis/fiber-api.md) · [All operations](https://skmtc.dev/fiber-ac/apis/fiber-api/llms.txt) · [OpenAPI document](https://skmtc.dev/fiber-ac/apis/fiber-api/revisions/58267250d793?raw)