Skip to main content
POST
Manage discard reasons
Use change_discard_reasons through MCP, or send this request directly. Read the selected task with get_discard_reasons first. The first reason creates a missing list. A reason can start with no subreasons. A required subreason must exist in the final saved list; replace the last one or disable the requirement in the same request. Deleting the last reason leaves an empty list. Renaming preserves codes. Recreating a deleted name gets a new code. Deleting a reason also removes its subreasons from the available choices; historical discards keep their recorded values. Duplicate names are rejected within the same list. The same subreason label may appear under different parents. Use set_reason_definition in the batch for atomic description changes across tasks. set_discard_reason_definitions remains available for one task; an empty string clears a description. Omitted properties stay unchanged. Read every selected task again after saving. If a response is lost, read before retrying. Changes across the selected tasks either all succeed or none is saved. New codes may need matching options in your external CRM. Configure those options separately; saving the Nexor list does not verify CRM synchronization.

Authorizations

X-API-Key
string
header
required

API key for authentication. Keys are prefixed with nxr_live_. To work inside a sub-account with a main account key, also send the optional X-Nexor-Sub-Account-Id header.

Body

application/json
workflow_ids
string<uuid>[]
required

Exact workflow IDs to change; never inferred from the account or group.

Required array length: 1 - 20 elements
changes
object[]
required

Ordered changes. Use exact existing codes from get_discard_reasons for edits and deletes.

Required array length: 1 - 100 elements

Response

Saved catalog

workflows
object[]
required
Last modified on November 12, 2026