---
title: "Perform Batch Operations"
method: PATCH
path: "/v2.0/flows/{flowId}/intents/{intentId}/sentences"
tags: ["Example Sentences"]
---

# Perform Batch Operations

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

Performs batch operations on [Sentences](https://docs.cognigy.com/ai/platform-features/nlu/intents/example-sentences) in an Intent.

## Path parameters

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

## Headers

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

## Request body

- object
  - `operations` union[]
    - union
      - object
        - `op` 'delete'
        - `id` string
      - object
        - `op` 'create'
        - `value` object — The payload for creating or updating an Example Sentence.
          - `text` string — The text in the Example Sentence.
          - `slots` union[] — The Slot segments in the Example Sentence. Each item defines a start and end indexes, and the Slot type: system-defined or user-defined Slot.
            - union
              - …
      - object
        - `op` 'update'
        - `id` string
        - `value` object — The payload for creating or updating an Example Sentence.
          - `text` string — The text in the Example Sentence.
          - `slots` union[] — The Slot segments in the Example Sentence. Each item defines a start and end indexes, and the Slot type: system-defined or user-defined Slot.
            - union
              - …

## Response `200`

Successfully ran the batch operations.

- object
  - `created` string[]
  - `updated` string[]
  - `deleted` string[]

## 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/revisions/85b2872bdfb7/schema)