---
title: "Update an Intent"
method: PATCH
path: "/v2.0/flows/{flowId}/intents/{intentId}"
tags: ["Intents"]
---

# Update an Intent

`PATCH /v2.0/flows/{flowId}/intents/{intentId}`

Update an Intent in a Flow. Allows modifying of an Intent's name, description, rules, tags, and status. You can also enable or disable the Intent, mark it as a reject Intent, adjust child/parent intent relationships, and override default reply settings.

## Path parameters

- `flowId` string, required
- `intentId` string, required

## Headers

- `Accept` 'application/json' | 'application/hal+json' | 'application/xml' | 'text/xml' | 'text/csv'

## Request body

- object
  - `name` string
  - `description` string
  - `condition` string
  - `rules` string[]
  - `isRejectIntent` boolean
  - `isDisabled` boolean
  - `tags` string[]
  - `confirmationSentences` string[]
  - `disambiguationSentence` string
  - `data` object
  - `localeReference` string
  - `childFeatures` union
    - boolean
    - string[]
  - `biasTowardsParentOrChildIntents` 'parents' | 'children'
  - `parentIntentId` string
  - `analyticsLabel` string
  - `overrideIntentDefaultRepliesAsExamples` 'on' | 'off' | 'useFlowSettings' — Toggle overriding the flow setting for using default replies as training examples

## Response `204`

Successfully updated Intent

## Other responses

- `400` — The server cannot or will not process the request due to something that is perceived to be a client error (e.g., malformed request syntax, invalid request message framing, or deceptive request routing)
- `401` — The request has not been applied because it lacks valid authentication credentials for the target resource.
- `402` — Upgrade your Plan to increase your Quota.
- `403` — The server understood the request but refuses to authorize it.
- `404` — The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.
- `405` — The method received in the request-line is known by the origin server but not supported by the target resource.
- `409` — The request conflicts with current state of the server.
- `413` — The request entity is larger than limits defined by server.
- `500` — The server encountered an unexpected condition that prevented it from fulfilling the request.
- `501` — The server does not support the functionality required to fulfill the request.
- `502` — The server, while acting as a gateway or proxy, received an invalid response from an inbound server it accessed while attempting to fulfill the request.
- `503` — The server is not ready to handle the request.
- `504` — The server, while acting as a gateway or proxy, did not receive a timely response from an upstream server it needed to access in order to complete the request.

---

[API](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.net/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/versions/85b2872bdfb7/schema)