---
title: "Generate NLU Scores"
method: POST
path: "/v2.0/projects/{projectId}/nlu/scores"
tags: ["Projects"]
---

# Generate NLU Scores

`POST /v2.0/projects/{projectId}/nlu/scores`

Generate a NLU score for an sentence by analyzing Intents in a Flow and Locale.

## Path parameters

- `projectId` string, required

## Request body

- object
  - `flowReferenceId` string, uuid, required — UUID of the flow reference.
  - `localeReferenceId` string, uuid, required — UUID of the locale reference.
  - `sentence` string, required — Sentence to analyze for NLU scoring.

## Response `200`

Returns a collection of matching NLU Intents and Scores for the given sentence.

- object
  - `scores` object[] — NLU scores based on the analysis.
    - `id` string — Unique identifier of the score.
    - `name` string — Name of the score type.
    - `score` number — Numerical value of the score.
    - `negated` boolean — Indicates if the score is negated.
    - `confirmationSentence` string — Sentence used to confirm the score.
    - `confirmationSentences` string[] — Multiple sentences for confirmation if applicable.
    - `disambiguationSentence` string — Sentence used for disambiguation.
    - `flow` string — UUID of the flow associated with the score.

## 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.dev/cognigy/apis/simulator-openapi-rest-ful-api-reference.md) · [All operations](https://skmtc.dev/cognigy/apis/simulator-openapi-rest-ful-api-reference/llms.txt) · [OpenAPI document](https://skmtc-service-production.skmtc.workers.dev/v1/apis/cognigy/simulator-openapi-rest-ful-api-reference/revisions/85b2872bdfb7/schema)